{"version":"2.1.323","anchor":"cloud-hosted-worker-detection-also-accepts-claude-code-remot","canonical_anchor":"cloud-hosted-worker-detection-also-accepts-claude-code-remot","heading":"More cloud sessions are now treated as hosted workers","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/cloud-hosted-worker-detection-also-accepts-claude-code-remot","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### More cloud sessions are now treated as hosted workers\n\nSetting CLAUDE_CODE_REMOTE with CLAUDE_CODE_ENVIRONMENT_KIND=anthropic_cloud now makes a session count as a hosted worker\n\n**Unclear.** It is not clear what Claude Code does differently once a session counts as a hosted worker.\n\n**What**\n\nClaude Code decides whether it is running as a hosted worker in the cloud. Before, it needed its own remote check to pass and `CLAUDE_CODE_REMOTE_SESSION_ID` to be set. It now also counts a session as a hosted worker when both of these environment variables (named settings a program reads when it starts) are set:\n\n- `CLAUDE_CODE_REMOTE` set to true\n\n- `CLAUDE_CODE_ENVIRONMENT_KIND` set to `anthropic_cloud`\n\n**Why**\n\nMore cloud sessions now fall under the hosted worker label than before.\n\n- Area: Cloud Sessions\n- Names: `CLAUDE_CODE_REMOTE_SESSION_ID`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}