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.234 Home All releases ←olderv2.1.233 v2.1.235newer→
Claude Code v2.1.234

Hosts must stay silent on dialog kinds they never declared

Under the hood
Useful2 Signal2
SDK

SDK hosts must stay silent on dialog kinds they never declared instead of replying cancelled.

What

The dialog protocol docs for SDK hosts were corrected. A host that receives a dialog_kind it did not declare must now leave the request unanswered rather than replying {behavior: "cancelled"}, because cancelled is a real settlement meaning the user dismissed the dialog.

Details
  • A kind is only sent to sessions where a client declared it in initialize.supportedDialogKinds.
  • On multi-client transports the request still reaches every attached client, so an undeclared kind can legitimately arrive at a host that cannot show it.
  • Dialogs left unanswered are cancelled by the CLI itself once the deadline passes.
Evidence

which is a real settlement treated as the user dismissing the dialog

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