{"version":"2.1.317","anchor":"resume-treats-a-hook-stopped-batch-as-a-deliberate-stop-beh","canonical_anchor":"resume-treats-a-hook-stopped-batch-as-a-deliberate-stop-beh","heading":"Resuming after a hook stopped a batch of tools may count as a deliberate stop","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/resume-treats-a-hook-stopped-batch-as-a-deliberate-stop-beh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Resuming after a hook stopped a batch of tools may count as a deliberate stop\n\nWhen a hook stopped a group of tool runs, resuming the session can treat it as a deliberate stop, behind a remote switch that is off by default\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 (pick up an earlier conversation), Claude Code looks at how the last turn ended. A new check looks for a hook having stopped Claude right after a group of tool results came back. If it finds one, the turn counts as a deliberate stop rather than an interrupted turn.\n\nThe check sits behind the remote switch `tengu_tidy_blanket`. It is off unless it is switched on remotely.\n\n**Why**\n\nOnce switched on, resuming a session that a hook stopped would no longer be treated as an interrupted turn that needs to carry on.\n\n- Flag `tengu_tidy_blanket`: Off in both readings (read for one account on one subscription tier against v2.1.317; this account: off, anonymous baseline: off, compiled default: off) 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: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}