{"version":"2.1.292","anchor":"telemetry-now-records-whether-a-session-has-a-remote-session","canonical_anchor":"telemetry-now-records-whether-a-session-has-a-remote-session","heading":"Usage data now notes whether a session runs remotely or in a container","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/telemetry-now-records-whether-a-session-has-a-remote-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Usage data now notes whether a session runs remotely or in a container\n\nClaude Code now records yes or no for whether a remote session ID or container ID is set\n\n**What**\n\nClaude Code now records a yes-or-no value in its usage data: whether `CLAUDE_CODE_REMOTE_SESSION_ID` or `CLAUDE_CODE_CONTAINER_ID` is set. It sits alongside the fields it already records about child sessions and how Claude Code was started.\n\n**Why**\n\nUsage data can now tell sessions running remotely or inside a container apart from local ones.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}