Repository checkouts, build artifacts, secrets, and any files a session creates or modifies all stay on infrastructure you provision. (View Highlight)
The conversation itself, including prompts, responses, and tool results (which can include code that Claude reads), is sent to Anthropic for inference, and the session transcript is stored so a session can be picked up from any surface. (View Highlight)
How it works
When using self-hosted environments, you deploy a set of runners. These long-lived processes pick up sessions and start a Claude Code process for each session. Runners come in two modes.
Fixed: you keep a set number running and sessions are distributed across them.
On-demand: an orchestrator watches for queued sessions, starts a runner as sessions arrive, and stops them when work finishes so capacity tracks demand.
Runners can serve more than one session, but each session runs in its own checkout, so work stays isolated between developers and accounts. Sessions from every supported surface route to the same environment, so you set it up once and it works wherever your team starts a session. (View Highlight)
Note: Self-hosted environments differ from Remote Control, which lets developers continue sessions running on their own machines from a phone or browser. Sessions using Remote Control end when that machine stops running the session and are tied to the user who ran claude, whereas self-hosted environments run sessions on shared infrastructure your platform team operates and can be used by any user. (View Highlight)
