Execution and isolation
Understand how LegionCode keeps each task isolated and why review remains required.
Each LegionCode run works in its own cloud workspace. This keeps tasks separated while still allowing you to review and decide what, if anything, should move back into your repository.
Isolated workspaces
Every run receives a separate checkout and execution context. Concurrent tasks can start from the same repository, but they do not share a writable working directory.
Isolation reduces accidental cross-task interference. It does not guarantee that two separate diffs will merge cleanly; you still review and reconcile the results.
Tools and filesystem
File reads, writes, commands, and Git operations are executed through the run workspace. Paths are resolved relative to that workspace and checked before use.
The event stream updates the conversation, tool activity, changed files, and review panel as work progresses.
Isolation is not approval
Sandbox isolation reduces blast radius. Permission policy and human diff review still decide whether an action is appropriate.
Review boundary
Treat generated changes as proposed code. Review the diff, run the checks required by your repository, and use explicit Git actions only when the result is acceptable.