Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.232 ·

Remote Control reattach checks who owned the conversation

Reattaching to Remote Control now verifies you own the conversation before reusing it.

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

Reattaching to a Remote Control conversation now verifies that the recorded owner is the account currently logged in. If it cannot be confirmed, Claude Code either refuses with a warning or attaches with history channels suppressed, rather than silently reusing the old pointer.

Details
  • Reattach now distinguishes a session named by the host from a restored pointer, and records why it reattached: owner match pinned, owner match, identity unreadable, or owner unknown.
  • Suppressing history channels means the reattached session does not replay prior conversation content.
Evidence

Host-directed reattach: this conversation\u2019s recorded owner could not be confirmed as the current login \u2014 attaching with history channels suppressed

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.232 →

Feedback