{"version":"2.1.236","anchor":"quitting-mid-prompt-leaves-the-question-for-the-next-session","canonical_anchor":"quitting-mid-prompt-leaves-the-question-for-the-next-session","heading":"Quitting mid-prompt leaves the question for the next session instead of denying it","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/quitting-mid-prompt-leaves-the-question-for-the-next-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Quitting mid-prompt leaves the question for the next session instead of denying it\n\nQuitting mid-question leaves that prompt pending for your next session instead of denying it.\n\n**What**\n\nWhen Claude Code has committed to shutting down, a pending permission request, tool approval or dialog is no longer cancelled or auto-denied. It is simply left unanswered so the next process can pick it up. Live for everyone on this build.\n\n**Details**\n\n- Internally the shutdown path hands back a promise that never settles, and the tool loop waits on the same thing at several points once exit is committed.\n- Replies that would answer this session's human are not injected; they are counted as replies left for the next process.\n- The old special-case machinery that parked \"ask user a question\" across shutdown is deleted in favour of this general rule.\n- New shutdown telemetry reports how many human requests were outstanding at exit.\n\n**Evidence**\n\n`tengu_shutdown_pending_state`, `this one is shutting down and settles no question`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}