{"version":"2.1.242","anchor":"hosts-must-declare-which-dialogs-they-can-show","canonical_anchor":"hosts-must-declare-which-dialogs-they-can-show","heading":"Hosts must declare which dialogs they can show","tier":"soon","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/hosts-must-declare-which-dialogs-they-can-show","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Hosts must declare which dialogs they can show\n\nEmbedding programs declare which dialogs they can show; unsupported ones are left to other clients.\n\n**What**\n\nA program embedding the cloud headless client lists the dialog kinds it can display in its `initialize` message, under `supportedDialogKinds`. Requests for an undeclared kind are not forwarded; the client prints a notice and leaves the dialog to another attached client or to the session's dialog timeout.\n\n**Details**\n\n- Permission requests are always forwarded regardless of what the host declared.\n- Skipped dialogs are counted as `dialogs_not_declared` at end of run.\n- The field is added to the honoured initialize options unconditionally.\n\n**Evidence**\n\n`its initialize did not declare the kind`\n\n- Area: Cloud Sessions\n- Names: `supportedDialogKinds`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5"}