{"version":"2.1.290","anchor":"remote-control-redacts-account-memory-from-sessions","canonical_anchor":"remote-control-redacts-account-memory-from-sessions","heading":"Remote Control no longer shows your account memory to remote clients","tier":"notice","area":"Remote Control","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/remote-control-redacts-account-memory-from-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Remote Control no longer shows your account memory to remote clients\n\nRemote Control now replaces or drops account memory content before sending session events and history to remote clients\n\n**Unclear.** Whether the filter is controlled by a remote setting, and what decides when it is switched off, is not known.\n\n**What**\n\nRemote Control lets you follow and drive a Claude Code session from another device. Claude Code now filters what it sends to those remote clients. Anything to do with account memory, which is information Claude keeps about you across sessions, is replaced with a placeholder or left out. This covers:\n\n- Calls Claude makes to read or write account memory, and their results\n\n- Attachments that carry memory\n\n- Memory entries in the session history\n\nThe session history uploaded when a session is forked, meaning copied into a new session, now goes through the same filter. Before, that history was sent unfiltered. The filter also has a mode that switches it off.\n\nIn the terminal session itself, memory content still shows as before.\n\n**Why**\n\nThis keeps memory content off remote devices. If you use Remote Control, you will see placeholders where memory activity would have appeared.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}