Skip to content
The Injection_
LIVE
LIVElast sweep next in--:--:--

[ RSS ][ JSON ][ llms.txt ]

INFOTool

External Sandbox: the coding agent stays outside the sandbox

External Sandbox gives Claude Code, Codex and Pi one localhost API for running their commands in a throwaway Linux guest.

· Prime Radiant · Research by Simon Willison, Prime Radiant

Claude Code
INFOTool

External Sandbox is a set of three Apache-licensed sandbox servers from Prime Radiant that run a coding agent's commands inside a Linux guest while the agent itself stays outside, behind a deny-by-default network proxy.

01What happened

Prime Radiant published External Sandbox on 16 November 2026 in a post credited to Simon Willison and written with the lab's team. The release covers three sandbox servers, a shared protocol with a conformance test runner, and agent integrations, all under Apache-2.0. Willison linked the post from his own blog the next day.

02How it works

The pattern keeps the agent on the host and sends only the commands it wants to run into a Linux guest, over one localhost HTTP and WebSocket API that all three servers implement. Each server mounts chosen directories read-write or read-only and starts with no network device at all. An allow-list proxy is the only way out: rules name an origin and the permitted HTTP methods, and the guest trusts the proxy's CA certificate so HTTPS can be filtered rather than tunnelled. A credential rule swaps a placeholder in the guest's request header for the real secret, which never enters the guest.

03Who is affected

Developers running Claude Code, Codex or Pi on macOS or Linux are the audience, with limits that differ per agent. Claude Code routes only its Bash tool through the sandbox, so its Read and Edit tools still act on the host and ignore the mount rules. Codex connects through its experimental exec-server protocol, tested against Codex CLI 0.164.0, and Pi needs version 1.5 or later plus the external-sandbox-pi extension. The v86 server runs anywhere with Node.js 22.19 or later, while the Apple Containers and Quicksand servers need an Apple silicon Mac.

04What to do

Mount a project read-only where the task does not need writes, and grant network access only through a proxy allow list naming the origins and methods a task really needs. Point credential rules at trusted services only, because the write-up warns that an allowed host could echo a substituted secret back in its response. Treat the servers as the author does, as experimental prototypes that have not been audited, and keep the work under version control.

Sources 4 links, all fetched

  1. 1blog.primeradiant.comLaunch Post
  2. 2github.comProtocol And Tests
  3. 3github.comv86 Sandbox Server
  4. 4simonwillison.netWillison's Note