Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.290 ·

Remote Control no longer shows your account memory to remote clients

Remote Control now replaces or drops account memory content before sending session events and history to remote clients

You'll notice Improvements
JSON All of v2.1.290
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
ImprovementsKind: in v2.1.290,
ImprovementsSection of the release

Unclear Whether the filter is controlled by a remote setting, and what decides when it is switched off, is not known.

What

Remote 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:

  • Calls Claude makes to read or write account memory, and their results
  • Attachments that carry memory
  • Memory entries in the session history

The 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.

In the terminal session itself, memory content still shows as before.

Why

This keeps memory content off remote devices. If you use Remote Control, you will see placeholders where memory activity would have appeared.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether the filter is controlled by a remote setting, and what decides when it is switched off, is not known.

See this entry in the whole of v2.1.290 →

Feedback