{"version":"2.1.280","anchor":"system-prompt-now-tells-claude-when-the-user-is-on-a-cloud-s","canonical_anchor":"system-prompt-now-tells-claude-when-the-user-is-on-a-cloud-s","heading":"Claude Code can now detect remote-control sessions and adjust guidance accordingly","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/system-prompt-now-tells-claude-when-the-user-is-on-a-cloud-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Claude Code can now detect remote-control sessions and adjust guidance accordingly\n\nClaude Code detects when it's running as a remote\/cloud session and warns Claude not to suggest files the user can't open\n\n**What**\n\nClaude Code can now tell when it's running as a remote-control session, reached for example through the Claude app, and changes its behavior for that case.\n\n- A new helper checks whether the process is a remote-control session by requiring `CLAUDE_CODE_REMOTE` to be truthy and `CLAUDE_CODE_ENTRYPOINT` to be one of `remote`, `remote_desktop`, `remote_mobile`, or `remote_trigger`.\n\n- When a session is a cloud session reached via the Claude app (detected via `CLAUDE_CODE_REMOTE` plus a `remote*` entrypoint), the system prompt now tells Claude that the user can only open files inside the primary working directory or the scratchpad\/memory directories, and instructs it not to present other file paths as something the user can open.\n\n**Why**\n\nIn a cloud\/remote session viewed through the Claude app, the user can't browse the full filesystem the way they could locally, so this keeps Claude from suggesting files or paths the user has no way to actually open.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}