A workspace for each run
The first local execution substrate uses Git worktrees and tmux. Delegating a node creates an isolated code workspace and a persistent executor. Its terminal can be attached from the browser. Closing the terminal leaves the run alive, and browser or server restarts recover live tmux sessions alongside pending reviews and outline state.
A common agent protocol
Coding agents use ACP through configured shims. The runner handles initialization, sessions, streamed updates, permission requests, and cancellation. The agent receives a scoped outline MCP server for reading context, proposing changes, and observing its run. A shell profile provides terminal-only execution.
Make the boundary visible
The run-scoped CLI and MCP API allow read, propose, and observe operations. They deny human mutation, review, remotes, and further delegation. This is an API ownership contract in a trusted local environment; it is not an operating-system sandbox. A local worktree isolates a checkout, while tmux keeps its process attachable.
Inspect, steer, return
The selected thread exposes context, activity, follow-up turns, Stop, and a collapsible terminal. Worktrees and branches remain available for manual review and cleanup after execution. The broader project also retains its exe.dev VM control plane. The local harness is the implemented starting point for the outline-centered workflow.