{"version":"2.1.295","anchor":"stdin-reader-can-pull-permission-answers-while-a-hook-runs","canonical_anchor":"stdin-reader-can-pull-permission-answers-while-a-hook-runs","heading":"Stop and permission answers are handled while an input hook is running","tier":"soon","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/stdin-reader-can-pull-permission-answers-while-a-hook-runs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Stop and permission answers are handled while an input hook is running\n\nClaude Code keeps reading input during slow input hooks, and withdraws pending permission requests when you press Stop or the session ends\n\n**What**\n\nHooks are actions you configure to run automatically at set points. Some run when new input arrives. Claude Code now keeps reading incoming messages while those hooks run, and sets them aside to handle afterwards.\n\nIf a permission request (a question asking whether Claude may take an action) is waiting when you press Stop or the session ends, it is now withdrawn. The model is told the request was withdrawn unanswered and should not ask again. When this behaviour is switched off, the hook simply runs as before.\n\n**Why**\n\nStop and permission handling stays responsive during a slow hook, mainly in headless sessions (run with no interactive screen) and remote sessions.\n\n- Flag `tengu_breezy_haven`: Not enough to say (read for one account on one subscription tier against v2.1.295; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Hooks\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}