Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.223 ·

Remote-stream notifications are namespaced, sanitized and capped

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

You'll notice New Features
JSON All of v2.1.223
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
New FeaturesKind: in v2.1.223,
New FeaturesSection of the release
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 →

Feedback