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.223 Home All releases ←olderv2.1.222 v2.1.224newer→
Claude Code v2.1.223

Peer message envelopes can carry a hop-chain attribute

Under the hood
Useful2 Signal0
Peer Messaging

Messages passed between peer sessions now record the path they took to get to you.

What

Delivered peer message envelopes can now include the chain of hops a message travelled, making previously internal routing state visible in the envelope itself.

Details
  • The envelope builder gained a fourth argument and emits a hop-chain="…" attribute alongside the existing from, from-session and from-name attributes when a validated chain is present.
  • The sender pulls the chain from the last peer-origin user message.
  • The hop-chain admission limits "hop-runaway" and "hop-loop" already existed; this only surfaces the chain in the envelope.
Evidence

hop-chain="

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.223 →