{"version":"2.1.296","anchor":"remote-environment-classifier-and-ccr-artifacts-endpoints","canonical_anchor":"remote-environment-classifier-and-ccr-artifacts-endpoints","heading":"Claude Code can tell which kind of remote environment it runs in","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/remote-environment-classifier-and-ccr-artifacts-endpoints","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Claude Code can tell which kind of remote environment it runs in\n\nClaude Code gains a check for which kind of remote environment it is in, plus addresses for an artifacts service\n\n**Unclear.** Nothing shows these addresses or the environment check being used by any feature yet.\n\n**What**\n\nClaude Code now has a check that sorts the environment it is running in into one of these kinds:\n\n- `tool_container_daemon`\n\n- `ccs_tenant`\n\n- `hosted_worker`, recognised by the `CLAUDE_CODE_REMOTE_SESSION_ID` environment variable being set\n\n- `none`\n\nIt also now holds two addresses for an artifacts service reached over MCP, the Model Context Protocol, a standard way of connecting extra tools: `\/v1\/code\/mcp\/ccr-artifacts` and `\/api\/artifacts\/mcp`.\n\n**Why**\n\nThese point toward support for an artifacts service in sessions that run on hosted machines.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}