{"version":"2.1.304","anchor":"dialogs-can-be-closed-by-a-new-prompt-new-dialog-telemetry","canonical_anchor":"dialogs-can-be-closed-by-a-new-prompt-new-dialog-telemetry","heading":"Waiting dialogs can now close when you type a new prompt","tier":"notice","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/dialogs-can-be-closed-by-a-new-prompt-new-dialog-telemetry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Waiting dialogs can now close when you type a new prompt\n\nDialogs opened through request_user_dialog can now close on their own when you send a new prompt, and can set their own waiting time\n\n**What**\n\n`request_user_dialog` is how Claude Code asks a connected app, such as one built with the SDK (the toolkit for building on Claude Code), to show you a question. It now accepts two options:\n\n- `closesOnNewPrompt`: the dialog is cancelled when you send a new prompt, with the reason recorded as `moved_on`\n\n- `parkTimeoutMs`: how long, in milliseconds, this dialog waits for an answer\n\nBefore, the waiting time came from one shared value for all dialogs. Claude Code also sends a new analytics event when a dialog is left showing, and dialog events carry extra details.\n\n**Why**\n\nA dialog no longer has to stay waiting after you have moved on and typed something new.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}