Source Intelligence
Follow Discord

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

Peer session lookup says when the local machine could not be listed

You'll notice
Useful2 Signal2
Cross-Session Messaging

If Claude can't list local sessions when routing a message, it says so instead of claiming no match.

What

When Claude Code cannot enumerate the sessions running on this machine while resolving which session to message, it now says so instead of implying no match exists.

Details
  • New messages: "the sessions on this machine could not be listed just now" and "this machine's and your account's other sessions could not all be checked just now".
  • The condition also blocks the shortcut that auto-picks a single obvious match, so you are asked rather than silently routed.
  • The same state is included in the diagnostic payload for the lookup.
Evidence

the sessions on this machine could not be listed just now

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.232 →