Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.224 Home All releases olderv2.1.223 v2.1.225newer

Remote sessions can run on self-hosted runner pools

Use it now
Useful3 Signal4
Self-Hosted Runner Notable

You can target your organization's own runner machines when starting a remote session.

/remote
What

Claude Code can now list your organization's self-hosted runner pools (machines your org runs itself rather than Anthropic-hosted ones) and target one for a remote session. Availability is decided by your organization's server-side configuration and first-party login; other auth returns an empty list.

Details
  • Pools come from /v1/code/runners/self-hosted/pools with the beta header ccr-byoc-2025-07-29, and each entry carries a pool id, name and a count of live runners.
  • A pool id prefixed ccpool_ is sent as the self-hosted pool target instead of the usual environment id.
  • A pool default coming from an untrusted source is ignored with a warning pointing at /remote-env, and a public Project rejects pools outright: public Projects run on Anthropic-hosted infrastructure only.
  • List outcomes are recorded with separate non-200, API-error and unexpected-response variants.
Evidence

ccr-byoc-2025-07-29, /v1/code/runners/self-hosted/pools

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.224 →