{"version":"2.1.295","anchor":"claude-code-remote-detection-no-longer-falls-back-to-another","canonical_anchor":"claude-code-remote-detection-no-longer-falls-back-to-another","heading":"Fewer situations count as running remotely","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/claude-code-remote-detection-no-longer-falls-back-to-another","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Fewer situations count as running remotely\n\nClaude Code's check for running as a remote session no longer falls back to a second test, so it now depends on `CLAUDE_CODE_REMOTE`\n\n**Unclear.** It is not known which situations the removed second test covered, so it is unclear who stops being treated as remote.\n\n**What**\n\nClaude Code has a check for whether it is running as a remote session, meaning on another machine rather than on your own computer. Before, it counted as remote if `CLAUDE_CODE_REMOTE` was set and another condition held, or if a separate second test passed. That second test has been removed, so the check now passes only when `CLAUDE_CODE_REMOTE` is set and the other condition holds.\n\n**Why**\n\nSome situations that used to count as remote may now not, which can change any behaviour that depends on running remotely.\n\n- Area: Sessions\n- Names: `CLAUDE_CODE_REMOTE`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}