{"version":"2.1.323","anchor":"tengu-tidy-blanket-gate-removed-hook-stopped-continuation-h","canonical_anchor":"tengu-tidy-blanket-gate-removed-hook-stopped-continuation-h","heading":"Hook-stopped turns now always count as a deliberate stop when you resume","tier":"notice","area":"Resume","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/tengu-tidy-blanket-gate-removed-hook-stopped-continuation-h","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Hook-stopped turns now always count as a deliberate stop when you resume\n\nThe check that treats a hook stopping Claude as a deliberate stop on resume no longer depends on a remote switch and always applies\n\n**What**\n\nA hook is a command you set up to run automatically while Claude Code works, and it can stop Claude from going on. When you resume a session, Claude Code checks whether a hook stopped Claude at the end of the last turn. That check used to apply only when the remote switch `tengu_tidy_blanket` was on. The switch has been removed and the check now always applies.\n\n**Why**\n\nBehaviour that was off unless switched on remotely now applies to everyone, so resumed sessions treat a hook stop as intended rather than as an interruption.\n\n- Flag `tengu_tidy_blanket`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.323; this account: on, anonymous baseline: on, compiled default: not a boolean we can read) 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: Resume\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}