Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.317 ·

Resuming after a hook stopped a batch of tools may count as a deliberate stop

When 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

Under the hood Internal Changes
JSON All of v2.1.317
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
Internal ChangesKind: in v2.1.317,
Internal ChangesSection of the release
What

A 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.

The check sits behind the remote switch tengu_tidy_blanket. It is off unless it is switched on remotely.

Why

Once switched on, resuming a session that a hook stopped would no longer be treated as an interrupted turn that needs to carry on.

Read from
Feature flag
tengu_tidy_blanket Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.317: 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.

Read once, for one account on one subscription tier, against v2.1.317. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns on for tengu_tidy_blanket, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_tidy_blanket

See this entry in the whole of v2.1.317 →

Feedback