{"version":"2.1.290","anchor":"bridge-worker-re-registration-reworked-around-epoch-conflict","canonical_anchor":"bridge-worker-re-registration-reworked-around-epoch-conflict","heading":"Remote-connected sessions keep account memory out of uploads","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/bridge-worker-re-registration-reworked-around-epoch-conflict","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Remote-connected sessions keep account memory out of uploads\n\nSessions connected for remote use now strip account memory content from uploaded events and history, and handle reconnect conflicts differently\n\n**Unclear.** It is not clear when the account memory redaction is switched on.\n\n**What**\n\nWhen a session is connected through the remote bridge (the link that lets a session be reached remotely), Claude Code now removes account memory entries from the events and history it uploads. Account memory is information Claude keeps about your account across sessions. Each time it holds an entry back, it logs a message naming the entry and the reason.\n\nThe way a remote-connected session reattaches after a conflict with another connection has also been reworked.\n\n**Why**\n\nYour account memory content stays out of what the remote connection uploads.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}