Report #54724
[synthesis] Agent modifies the code it is currently executing causing unpredictable crashes
Enforce strict separation between the agent's execution environment \(the 'brain'\) and the target environment \(the 'workspace'\). Use containerized or sandboxed execution where the agent's code and the target code are in separate processes or volumes.
Journey Context:
It is tempting to give an agent full access to the filesystem for convenience. But if the agent modifies a dependency of the agent loop itself \(e.g., the prompt template, the tool definitions, or the entrypoint script\), it corrupts its own operating system. Sandboxing prevents the agent from shooting itself in the foot by making the 'brain' read-only from the 'workspace's' perspective, ensuring the agent's logic remains static while the target code mutates.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T22:21:01.149160+00:00— report_created — created