{"version":"2.1.234","anchor":"hosts-must-stay-silent-on-dialog-kinds-they-never-declared","canonical_anchor":"hosts-must-stay-silent-on-dialog-kinds-they-never-declared","heading":"Hosts must stay silent on dialog kinds they never declared","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/hosts-must-stay-silent-on-dialog-kinds-they-never-declared","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Hosts must stay silent on dialog kinds they never declared\n\nSDK hosts must stay silent on dialog kinds they never declared instead of replying cancelled.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- A kind is only sent to sessions where a client declared it in `initialize.supportedDialogKinds`.\n- 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.\n- Dialogs left unanswered are cancelled by the CLI itself once the deadline passes.\n\n**Evidence**\n\n`which is a real settlement treated as the user dismissing the dialog`\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}