Sandbox
The Sandbox lets you run a prompt without betting your main branch on it. Each sandboxed prompt executes in its own isolated git worktree; when it finishes, you look at the result and decide whether it earns a place in your real history.
Sessions in worktrees
Section titled “Sessions in worktrees”A sandbox session is a per-prompt git worktree. You route a prompt into it from the New Prompt modal’s “Run In: Live | Sandbox” selector, or by pointing a queued prompt at a specific healthy session. When the work is done you have three choices: Promote it (merge into your default branch through a throwaway temp worktree), Discard it, or View Cumulative Diff to see everything the session changed before deciding.
If a session ever freezes, several escape hatches get you out: a titlebar button, a banner action, the Ctrl+Shift+X shortcut, and an automatic exit after three failed starts. AI clients can also list stored sandbox sessions and route a prompt directly to a healthy one — and an invalid or non-runnable session id fails loudly rather than silently falling back to the live queue.
The server sidecar
Section titled “The server sidecar”For heavier isolation, Orbit can run a full second server as a child process bound to its own data directory (~/.orbit-sandbox/) on its own port, with its own queue. The New Prompt modal’s Live | Sandbox switch routes prompts to it, giving you a complete parallel environment for risk-free experiments.
Cleanup
Section titled “Cleanup”Sandboxes leave artifacts — worktrees, branches, session rows — and Orbit watches for orphaned ones in the background, offering per-item Clean Up or Ignore under Settings → Queue & Sessions → Sandbox.