{"version":"2.1.247","anchor":"remote-tool-forwarding-now-has-its-own-admission-check","canonical_anchor":"remote-tool-forwarding-now-has-its-own-admission-check","heading":"Remote tool forwarding now has its own admission check","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/remote-tool-forwarding-now-has-its-own-admission-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Remote tool forwarding now has its own admission check\n\nWhether a session may forward tools to a remote worker is now decided by its own check up front.\n\n**What**\n\nWhether a session may forward tool calls to a remote worker is decided up front by a dedicated check, matching how hooks and plugins are already admitted, and the answer is passed into headless startup.\n\n**Details**\n\n- Requires an SDK URL, a `CLAUDE_CODE_REMOTE_SESSION_ID`, no `CLAUDE_CODE_ENVIRONMENT_KIND`, an allow-listed entrypoint, a live session channel, and a non-hermetic session.\n- Refusals carry one of four reasons: `not_managed_cloud_worker`, `entrypoint`, `session_channel_off` or `hermetic`.\n\n**Evidence**\n\n`return { admitted: !1, reason: \"not_managed_cloud_worker\" };`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}