SANDBOXES FOR CODING AGENTS

Let agents loose.
Safely.

Scared of getting pwned because your agent has the same privileges as you?

Run many coding agents at once, on your own machines, each fully isolated. You stay in control.

  • MIT
  • docker · podman · Apple container
  • Linux · macOS

Diagram: on your machine, the devsandbox dashboard is connected to three sandboxes, web, web-2 and web-3. Each is its own container with an agent you run inside it: web uses your checkout in ../web, web-2 and web-3 their own git worktrees on branches sandbox/web-2 and sandbox/web-3. All three share one postgres service. From the dashboard you open any sandbox in VS Code, attached to its container.

Arrow keys or j and k select an instance, o opens it in VS Code, Escape closes VS Code, t opens a terminal on it, s stops or starts it, d removes it (or cancels its build), l shows its logs, b its build log, p forwards a port, Enter opens the config explorer, colon opens the command prompt where Tab completes and Escape cancels, left and right arrows or 1 to 4 switch tabs, question mark shows help. In a terminal, keys go to the shell and Escape returns to the dashboard; square brackets switch terminals and x closes one. Tab leaves the preview.

1 sandbox · 3 running / 0 stopped · 1 service container · docker 27.3.1
Instances
TREESTATUSUPTIMEFOLDER
▾ web3/3 runningimage node:22 ../web
webrunning2h05m../web
web-2running48m⎇ .worktrees/web-2
web-3 ✉1running12m⎇ .worktrees/web-3
Detail
container: devsandbox-web
workspace: /workspaces/web
agents: 1
base folder: ../web
selectconfigvscodestoplogsbuild logforwardrmtermcmdswitchhelp
  1. 01

    Define sandboxes once

    A devsandboxes.toml names the image, your repo folder and the services, like postgres.

  2. 02

    One sandbox per agent

    Each devsandbox run starts a container on its own worktree and branch. Start your agent inside it.

  3. 03

    Watch and jump in

    The dashboard shows every sandbox and the notifications sent from inside. Press o to open one in VS Code.

WHAT YOU GET

Everything an agent needs.
Nothing it shouldn't have.

MENU /
View on GitHub
EXAMPLES
All examplesEvery recipe on one page.Parallel coding agentsSeveral coding agents on one repo, fully isolated from one another.One shared PostgresOne development database for all your sandboxes and their instances.Private services per instanceEvery instance gets its own Postgres and Redis, so agents never touch each other's data.Shared package cachesNew sandboxes stop downloading the same packages again.ssh-agent and git pushAgents push over ssh with your host's keys, which never enter the container.Port forwarding on demandOpen a sandbox's dev server or database from your host, without restarting anything.Attach VS CodeOpen any instance in VS Code with one key.devcontainer FeaturesAdd Node, Rust or the GitHub CLI to any image, in TOML.Babysit pull requestsAn agent keeps your open PRs merged with their base, and pings you when it can't.Port a devcontainer.jsonTurn an existing devcontainer.json into a devsandbox config.