Self-Healing and Self-Evolution
Zero dead ends -- the agent repairs and improves itself.
ZYRAXON’s most distinctive capability: if a tool is missing, it installs one. The agent does not stop at a failure; it looks for another route, retries with backoff, and reports what it did instead of surfacing a dead end.
The healing loop
- 01You request something that needs a tool ZYRAXON does not have.
- 02The agent checks its currently available tools.
- 03It searches online for a suitable MCP server, npm package or script.
- 04It installs and configures the missing capability.
- 05The task resumes immediately with the new tool.
Self-evolution
Beyond healing, ZYRAXON proactively improves itself at runtime -- installing its own MCP servers and building new tools when it detects repeated needs. The self_evolve built-in tool drives this loop, writing a new tool and registering it without a restart.
What it recovers from
| Failure | Recovery |
|---|---|
| Missing tool | Searches, installs and configures it |
| Failing test | Diagnoses the cause and fixes it |
| Code that will not run | Works on it until it does |
| Dropped MCP connection | Reconnects; the Effect runtime releases the dead resource |
| Machine restart | Every session is persisted; the next run resumes where it stopped |