Skip to main content

​
Overview

Remote sandboxes run your session in a managed cloud container while keeping the same context and workspace. When a session runs in Sandbox, Omnara restores your workspace from a synced checkpoint, runs any workspace setup scripts, and reconnects the session.
Reminder: You can run sessions locally and control them from your phone without using cloud sandboxing. Use sandboxing when you want execution itself to move off your machine.

​
Requirements

GitHub connected for the workspace

​
Using Sandboxes

There are two ways to use Sandbox:
  1. In the sidebar, click the cloud icon next to a worktree name to move that session to Sandbox. Wait for the sandbox to start, migrate, and reconnect.
  2. You can also start a brand new session directly in Sandbox from the new session screen. This is not a migration, but it uses the same sandbox environment.

​
Migrate Back to Local

Switch the execution target back to Local from the same UI.

​
Notes

  • sandbox sessions run from the restored workspace state
  • git operations in the sandbox use the GitHub access you connected through Omnara for that workspace
  • local and sandbox execution are different environments

​
Common Confusion

​
“Why is Sandbox unavailable?”

Usually this is because GitHub access has not been enabled for the workspace yet. To enable it:
  1. Click Workspace Settings using the gear icon next to the worktree name
  2. Select the Git tab and connect GitHub

​
“Does Sandbox use my git credentials?”

Yes. Sandbox git operations use the same GitHub access you connected Omnara with.

​
“Does Sandbox use my local Claude Code or Codex subscription?”

No. Cloud sandboxes use Omnara-managed cloud credits instead of spending through your local Claude Code or Codex setup. You can see how many Cloud Sandbox Credits you have left in Settings → Billing.

​
“Will Sandbox see my local services?”

No. Local and sandbox execution are different environments.