{"version":"2.1.224","anchor":"remote-sessions-can-run-on-self-hosted-runner-pools","canonical_anchor":"remote-sessions-can-run-on-self-hosted-runner-pools","heading":"Remote sessions can run on self-hosted runner pools","tier":"use","area":"Self-Hosted Runner","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/remote-sessions-can-run-on-self-hosted-runner-pools","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Remote sessions can run on self-hosted runner pools\n\nYou can target your organization's own runner machines when starting a remote session.\n\n**What**\n\nClaude 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.\n\n**Details**\n\n- 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.\n- A pool id prefixed `ccpool_` is sent as the self-hosted pool target instead of the usual environment id.\n- 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.\n- List outcomes are recorded with separate non-200, API-error and unexpected-response variants.\n\n**Evidence**\n\n`ccr-byoc-2025-07-29`, `\/v1\/code\/runners\/self-hosted\/pools`\n\n- Area: Self-Hosted Runner\n- Names: `\/remote`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 4\/5"}