Unclear Which MCP end-of-turn requests fall into the kind that stop hooks can now block is not stated.
What
A hook is a command you configure to run at certain points. A stop hook runs when Claude is about to finish its turn. MCP (Model Context Protocol) servers are add-ons that give Claude extra tools, and they can ask for a turn to end. This release adds a new code path for those requests.
- A new helper returns true only when the requested stop is
mcp_meta_blockable, the current step is not the last one, and the gatetengu_glittery_mittenis on. A gate is a remote switch Anthropic uses to turn features on for some users. - If looking up the gate fails with an error, the helper reports
query_mcp_end_turn_stop_hooks/gate_threwand returns false. - A companion helper logs
[end-turn] bookkeeping threw and was skipped:when its bookkeeping fails, and carries on. query_mcp_end_turn_stop_hookswas also added to a list of names that looks like a list of behaviour flags.
Nothing has been read about tengu_glittery_mitten, so whether it is on is unknown.
Why
In practice this may let stop hooks act on end-of-turn requests from MCP servers. When the gate check fails, it is treated as off, and a failure in the extra bookkeeping does not end the turn early.
tengu_glittery_mitten Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.302: 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.
Read once, for one account on one subscription tier, against v2.1.302. It isn't a statement about your account. What a flag value here can and cannot tell you
Which MCP end-of-turn requests fall into the kind that stop hooks can now block is not stated.
New in this build: tengu_glittery_mitten