{"version":"2.1.304","anchor":"request-user-dialog-may-be-sent-with-no-deadline","canonical_anchor":"request-user-dialog-may-be-sent-with-no-deadline","heading":"SDK dialogs from Claude Code can now stay open with no deadline","tier":"notice","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/request-user-dialog-may-be-sent-with-no-deadline","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### SDK dialogs from Claude Code can now stay open with no deadline\n\nClaude Code may now send a `request_user_dialog` with no deadline, which stays open until answered or withdrawn with `control_cancel_request`\n\n**What**\n\nPrograms that drive Claude Code through the SDK (a host application that talks to Claude Code instead of a person typing) receive `request_user_dialog` messages when Claude Code needs the user to answer something. The description of that message now says Claude Code may send one with no deadline.\n\nSuch a dialog stays up until it is answered, or until Claude Code withdraws it with a `control_cancel_request`. Before, an unanswered dialog was always cancelled once its deadline passed.\n\n**Why**\n\nSDK hosts can no longer count on every dialog timing out on its own. A host has to be able to keep a dialog open indefinitely and close it when Claude Code sends a cancel.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}