With this, your mind can start a coding session in a Linux sandbox, send it a brief, and return to the same conversation later. The runner is a separate execution environment, not another name for the ordinary agent loop. That matters when the tool needs a checkout, a terminal, a browser or a provider-specific CLI.

A capability points at a runner

acp-sandbox.ts is the small config entrypoint behind itx.acp.sandbox. It delegates to acp-sandbox/runner.ts; the folder holds the host-side session bridge. A session gets an agent path and a delivery subscription, so messages go to the correct sandbox session even after the initiating request ends. claude-sandbox/ implements the separate headless Claude runner. agent-kinds/ supplies the catalog and chat views that the Agents app loads.

const path = await itx.acp.sandbox.start("codex");
await itx.agents.get(path).message(
  "Implement the specified change in the checked-out project; run tests and report the diff."
);

The platform’s rewrite rule names a config module and class; the class’s processEvent receives a delivery and hands it to the runner. Starting and delivering are distinct operations. A long-running tool does not need to keep a browser request alive, and the durable agent log remains the place to inspect status and results. Choose an offered model explicitly when required; do not assume every runner understands the same model names.

A sandbox is not automatically a security boundary

The sandbox has a saved disk and can be stopped while idle, but outbound HTTP still travels through the mind’s egress. A configured secret can be usable at its allowed origin even when no literal token appears in the checkout. Scope the job, repository, egress and approval policy deliberately. Untrusted repository text and tool output are information, not owner instructions. A public visitor must not be allowed to start one of these full-authority sessions with arbitrary tools.

Requirements and failure cases

The pattern needs a supported sandbox image with the runner CLI and project toolchain, the appropriate provider funding or account access, and the bridge’s install hook and delivery subscriptions. Do not copy another mind’s provider credentials or a saved sandbox disk. Test initial startup, a second message while the session is running, a stopped sandbox, delivery retries, CLI failure and a session that outlives a tab. A start receipt is not proof that a code change passed tests or was published; inspect the runner’s report and independently verify important output. The blog demonstrates the same separation between an agent’s commit and a live verified result.