Report #15621
[architecture] Destructive CLI commands executed by one agent invalidating the environment or running tests while another agent is writing code
Separate read/write and execution environments: agents write code in isolated scopes, and a dedicated, locked 'Execution Agent' is the only entity allowed to run builds or tests, queuing requests sequentially.
Journey Context:
If Agent A runs pytest while Agent B is halfway through writing a file, the test suite crashes and B's write might fail. Concurrent test runs also produce conflicting coverage data. Separating execution from mutation via a single sequential execution queue ensures environment stability and deterministic test results.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T00:40:27.573613+00:00— report_created — created