Anthropic has moved self-hosted environments for Claude Code into public beta, giving organizations on its Team and Enterprise plans the option to run coding agent sessions on infrastructure they control. The feature allows sessions started through the web, mobile and desktop apps, or through a routine, to run within an organization’s network rather than on Anthropic-hosted infrastructure. That can place Claude Code alongside internal databases, registries, development tools and security controls without making those systems available through the public internet. Organizations can also pre-install compilers, software development kits and internal command-line tools for use during sessions. Repository checkouts, build artifacts, secrets and files created or modified during a session stay on the infrastructure provisioned by the organization. The conversation itself, including prompts, responses and tool results that may contain code read by Claude, is sent to Anthropic for inference. Session transcripts are also stored so work can be resumed from different supported devices and applications. Organizations using the feature deploy runners, which are long-running processes that collect queued sessions and start a separate Claude Code process for each one. Anthropic provides two runner models: fixed deployments maintain a set number of runners and distribute sessions between them, while on-demand deployments use an orchestrator to start runners when sessions enter the queue and stop them when the work is complete. A runner can handle more than one session, but each session receives its own repository checkout. Sessions started through any supported interface are directed to the same self-hosted environment, differing