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

Clearer addressing rules and failure notes for cross-session messages

You'll notice
Useful3 Signal2
Session Messaging

Cross-session messaging now explains when a bare name works and when you need a ref.

What

Sending a message to another agent or session now explains when a bare name is enough and when it is not: an exact match against a single live agent or session delivers directly, while a typed prefix or an unavailable session list means you must supply a ref.

Details
  • The agent listing now warns separately when the cloud session list could not be fetched and when the local machine list could not be fetched, so you know which half may be short.
  • The listing states that a cloud session cannot message you back yet.
  • Results carry a separate display string, and notes call out same-named siblings.
  • Telemetry gained exactUnique and previouslyPinned attributes on send attempts.
Evidence

The cloud session list could not be fetched just now, so this list may be missing a cloud session; retry if you meant one.

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 →