{"version":"2.1.236","anchor":"hooks-and-ctrl-c-go-quiet-once-shutdown-has-started","canonical_anchor":"hooks-and-ctrl-c-go-quiet-once-shutdown-has-started","heading":"Hooks and Ctrl-C go quiet once shutdown has started","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/hooks-and-ctrl-c-go-quiet-once-shutdown-has-started","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Hooks and Ctrl-C go quiet once shutdown has started\n\nOnce you quit, hooks stop firing except SessionEnd and Ctrl-C no longer aborts the request.\n\n**What**\n\nAfter shutdown is committed, every hook event other than `SessionEnd` stops running, and pressing Ctrl-C no longer aborts the in-flight request. Your `PostToolUse` and other hooks will not fire during an exiting session.\n\n**Details**\n\n- A commit latch is set by the synchronous shutdown path; hook dispatch then waits on a promise that never resolves, both before dispatching and before returning results.\n- `SessionEnd` is the sole exception, so end-of-session hooks still run.\n- The REPL interrupt handler becomes a no-op for the duration, so Ctrl-C during shutdown does nothing rather than cancelling.\n\n**Evidence**\n\n`hookEventName: wt(\"PostToolUse\")`\n\n- Area: Hooks\n- Names: `SessionEnd`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}