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

Remote-stream notifications are namespaced, sanitized and capped

You'll notice
Useful2 Signal0
Remote Control

Notifications sent from remote peers are now trimmed, capped and prefixed so they can't flood your queue.

What

Notification frames arriving over a thin-client or remote stream are normalized through a shared mapper before they reach the local notification queue, so a remote peer cannot flood or corrupt it.

Details
  • Keys are prefixed with remote:, text has whitespace collapsed and is truncated, and timeout_ms is clamped.
  • Colors that collide with Object.prototype are rejected, and priority "immediate" is downgraded to "high".
  • A queue cap evicts the oldest remote: notification.
  • Malformed frames are dropped and logged as "[useThinClientSession] Dropping malformed notification frame".
  • Routing outcomes are reported via tengu_remote_notification_routed.
Evidence

[useThinClientSession] Dropping malformed notification frame

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