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

Agent-to-agent messaging says when the local agent list could not be read

You'll notice
Useful2 Signal2
Session Messaging

A failed local agent lookup is now reported as a failure, not as "no such agent".

What

Sending a message to another agent already distinguished the cloud directory and the bridge being unreachable. A third case, the local agent registry failing to answer, is now tracked and shown in the "not sent" line, so a lookup failure is no longer reported as if no such agent existed.

Details
  • The new flag is localUnavailable, carried through routing, suggestion suppression and the message shown to you.
  • Listing peers similarly gained a cloudListFailed flag.
Evidence

localUnavailable

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 →