Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.232 Home All releases olderv2.1.231 v2.1.233newer
Claude Code v2.1.232

Remote Control reattach checks who owned the conversation

You'll notice
Useful3 Signal3
Remote Control

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

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 →