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

A SubagentStop hook now fires when a subagent finishes, alongside the existing SubagentStart hook

TierUse it nowhow much it should matter to you
Useful4my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaHookswhat it touches
KindNew Featuresin v2.1.275,
Use it now Notable

A SubagentStop hook now fires when a subagent finishes, alongside the existing SubagentStart hook

What

Hooks are user-configured scripts that run automatically at specific points in Claude Code's operation. The internal hook-event handling now treats SubagentStop the same way it already treats SubagentStart, which means a Stop-style hook can now fire when a subagent (a separate Claude instance handling a sub-task) finishes, not just when one is spawned.

Why

This gives users a way to run a hook specifically when a subagent completes its work, complementing the existing SubagentStart hook that fires when one is spawned.

Read from
Names in the bundleSubagentStop
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up SubagentStop, on Hooks reference. Not every SubagentStop event comes from a subagent Claude spawned. Claude Code also runs internal agents for some of its own features, such as [prompt suggestions](/docs/en/interactive-mode#prompt-suggestions) and [`/btw` side questions](/… hooks see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up SubagentStop, on Hooks reference.
Anthropic's release notes agreeFixed SubagentStop hooks with a specific matcher firing for every stopping subagent whose agent type was empty

See this entry in the whole of v2.1.275 →

Feedback