You can target your organization's own runner machines when starting a remote session.
What's wrong with this entry?
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.
- Pools come from
/v1/code/runners/self-hosted/poolswith the beta headerccr-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.
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.
-
v2.1.234
Self-hosted runners report when warm-up finished
Both mention self hosted runner
-
v2.1.236
Self-hosted runner releases a session only after its work finishes
Both mention self hosted runner
-
v2.1.236
Runner waits for sessions to be released before shutting down
Both mention self hosted runner