---
title: "Introducing Coding Agents: a runner behind a durable conversation"
summary: "Coding sessions can live in sandboxes while the mind keeps the thread, delivery and model choice together."
created: "2026-11-15"
updated: "2026-11-17"
revision: "4"
previous: "2c9ed816cae734a87f481d225882d081445f5e99"
reviewedThrough: "db9c004f146ca49dc313bc6b0a28d308d0d4b824"
sourceDigest: "9bb981ad3b9448472f508dc3404dd9ab864c92d382c8c7bd5df6e792749d0d85"
---

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](/introducing/agents) loads.

```js
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.

## Coordinate ownership before starting another session

A durable conversation does not prevent two agents from changing the same file. In this mind, a coding chief of staff reads the active-agent catalog, routes requests to the agent that owns an area, and keeps a durable merge and deploy queue. Its role guide is `coding-chief-of-staff.md`. Rebuild the convention with your own area owners, not a copy of another team's live session identifiers. Record assignments and outcomes as events, ask an existing owner before creating overlapping work, and return both an initial ownership receipt and a final result. This coordination is separate from the runner and does not grant deployment approval. The sample start call above illustrates the transport, not permission to bypass that queue.

## Name the session without changing its authority

The shared worker also calls `agent-titler.ts` for supported coding-session events. Near the start of a new session, it finds the first eligible prompt, checks that no explicit summary title exists, and claims a single naming request durably. One small model call through the mind's AI Gateway receives only a bounded prefix of that prompt. A validator accepts a short, single-line title and appends a title-only summary update; it neither executes the prompt nor starts coding work. A manually set title is not deliberately replaced, and a later owner title wins. Invalid output, timeout or provider failure leaves the fallback name and records an error without retrying. Rebuilders should test duplicate events, existing owner names and model failure, and include this small model dependency in their privacy and funding review.

## 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](/introducing/blog) demonstrates the same separation between an agent’s commit and a live verified result.
