CodeWork
Sandboxes

Local

The default sandbox. Your folder and your real shell.

How It Works

local is the default driver. It binds the agent directly to your machine: file tools use your real filesystem, starting in the current directory or in --cwd, and bash runs real commands through bash (sh when bash is not on PATH) with the environment CodeWork started with.

Anything you have installed, such as git, node, or your test runner, the agent can use. There’s nothing to provision, so it’s the fastest sandbox, and the only one that works on your repository without copying anything.

Use it when your machine is the workspace: everyday coding in your own repository, with your own toolchain.

What It Can Reach

There is no isolation, by design. The working directory is a starting point, not a fence. The agent can:

  • Read and write files anywhere your user account can.
  • Use any API keys or tokens exported in your shell.
  • Reach the network, other processes, and anything else your shell can.

Interrupting a turn sends SIGTERM to a running command, then SIGKILL a second later.

--sandbox-provider-id doesn’t apply to local. Passing it is an error.

Work Safely

  • Use git and start from a clean tree. The agent’s changes then show up alone in git diff, and git restore and git clean undo them.
  • Review the diff before you commit.
  • Keep secrets out of the environment. Don’t export credentials the task doesn’t need.