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.229 Home All releases ←olderv2.1.228 v2.1.231newer→
Claude Code v2.1.229

SDK clients are told the CLI accepts queued notifications

Under the hood
Useful1 Signal3
SDK not in their notes

SDK clients now learn during handshake that the CLI can accept queued notifications.

queued_notifications
What

The init handshake a client gets over the SDK control protocol now advertises a third capability value, queued_notifications, meaning the CLI accepts inbound queued notification stream messages and drains them on request.

Details
  • Documented as read by the backend from the persisted init event to decide whether it may send such messages.
Evidence

'queued_notifications' = the CLI accepts inbound queued_notification stream messages and drains them via ReadNotifications

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