Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.271 ·

Plugin/hooks dispatch runtime adds a shared 'answering' async context

Plugin and hook dispatch code adds a shared 'answering' tracking context around interface calls

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaPluginswhat it touches
KindInternal Changesin v2.1.271,
Under the hood

Plugin and hook dispatch code adds a shared 'answering' tracking context around interface calls

What

The internal system that dispatches plugin and hook interactions now wraps its calls in a new "answering" tracking context, and the underlying press function now tracks whether each call is still active via a new liveness flag that clears once the call finishes.

Why

This is internal plumbing for tracking in-flight plugin/hook interactions; it's not described as changing anything a user would see directly.

How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed the interactive /hooks menu crashing when a hook matcher is named after an inherited object property such as __proto__ or constructor

See this entry in the whole of v2.1.271 →

Feedback