{"version":"2.1.275","anchor":"subagentstop-hook-event","canonical_anchor":"subagentstop-hook-event","heading":"SubagentStop hook event","tier":"use","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/subagentstop-hook-event","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### SubagentStop hook event\n\nA SubagentStop hook now fires when a subagent finishes, alongside the existing SubagentStart hook\n\n**What**\n\nHooks 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.\n\n**Why**\n\nThis 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.\n\n- Area: Hooks\n- Names: `SubagentStop`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}