{"version":"2.1.293","anchor":"remote-transport-persistenceredaction-checks-and-a-settings","canonical_anchor":"remote-transport-persistenceredaction-checks-and-a-settings","heading":"Stricter checks on what remote sessions can save","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/remote-transport-persistenceredaction-checks-and-a-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Stricter checks on what remote sessions can save\n\nRemote sessions now save data only when CLAUDE_CODE_REMOTE_SESSION_ID is set and the session came from an allowed remote entry point\n\n**Unclear.** It is not clear what these checks control in practice.\n\n**What**\n\nClaude Code has changed checks that decide whether a remote session's connection may save data. A remote session is one run on another machine. Saving is allowed only when both hold:\n\n- `CLAUDE_CODE_REMOTE_SESSION_ID` is set\n\n- the session was started from one of two remote entry points, one of which is mobile\n\nThe check also takes into account whether the connection hides sensitive parts of what it saves. A second check now gives a result only for local connections or for one particular kind of remote connection.\n\n**Why**\n\nThis narrows what remote sessions save.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}