{"version":"2.1.307","anchor":"remotessh-spawned-detection-helpers-added","canonical_anchor":"remotessh-spawned-detection-helpers-added","heading":"Changed detection of sessions started by a server or over SSH","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/remotessh-spawned-detection-helpers-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Changed detection of sessions started by a server or over SSH\n\nClaude Code treats a session as server- or SSH-started when CLAUDE_CODE_SPAWNED_BY_SERVER, CLAUDE_SSH_DAEMON_CHILD or CLAUDE_SSH_RUN_DIR is set\n\n**Unclear.** It is not shown what Claude Code does differently once a session counts as a remote relay.\n\n**What**\n\nClaude Code's checks for how a session was started have changed. SSH is a way of working on another computer over the network.\n\n- A session counts as started by a server or over SSH when any of `CLAUDE_CODE_SPAWNED_BY_SERVER`, `CLAUDE_SSH_DAEMON_CHILD` or `CLAUDE_SSH_RUN_DIR` is set.\n\n- A second check also counts the session as a remote relay when `remoteRelayMark` is not set to false or when Claude Code was started through the `ssh-remote` entry point.\n\n**Why**\n\nSetting any of these environment variables makes Claude Code count the session as started by a server or over SSH.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}