{"version":"2.1.246","anchor":"host-dialogs-go-through-one-checked-dispatcher","canonical_anchor":"host-dialogs-go-through-one-checked-dispatcher","heading":"Host dialogs go through one checked dispatcher","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/host-dialogs-go-through-one-checked-dispatcher","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Host dialogs go through one checked dispatcher\n\nDialogs shown by your editor now fall back to a safe default when anything goes wrong.\n\n**What**\n\nRequests for a dialog on the user's machine now validate both the question and the answer against a schema, and fall back to the dialog's declared default whenever the host does not support that dialog, the question is malformed, the user cancels, or the answer does not parse.\n\n**Details**\n\n- Every case is logged with an outcome (undeclared, invalid_payload, cancelled, invalid_result, answered) and a latency measurement.\n- The client refuses to forward its own directory-sync consent dialog back from the cloud session.\n\n**Evidence**\n\n`tengu_remote_headless_client_host_dialog`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}