Proposed change

If the agent dies for any reason, there's no way to respawn it - the nex node dies with it. The only recovery is to restart nex, and then redeploy (even though the scripts / binaries are already in the NEXCLIFILES object store bucket). If the agent some way of recovering from a critical failure, it would make nex a lot more resilient.

Use case

Most things would work nicely, however, I could write a script that causes the runtime engine to crash out (perhaps by consuming too much memory, or a network timeout issue when connecting remotely). If nex could trigger an agent restart and redeploy the things that were on the failing node, it would help.

Contribution

No response