{"version":"2.1.269","anchor":"turncomplete-telemetry-only-fires-when-a-hook-wants-it","canonical_anchor":"turncomplete-telemetry-only-fires-when-a-hook-wants-it","heading":"turn.complete telemetry only fires when a hook wants it","tier":"soon","area":"Plugin Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/turncomplete-telemetry-only-fires-when-a-hook-wants-it","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### turn.complete telemetry only fires when a hook wants it\n\nA new `turn.complete` hook reports a turn's final answer, refusal, usage and error state, but only when a plugin listens for it\n\n**What**\n\nClaude Code can now assemble a summary of each completed turn (the final answer, whether it was refused, token usage totals, and whether it was aborted or errored) and send it to a `turn.complete` hook. This only happens if a loaded plugin actually registers a `turn.complete` hook; otherwise the work is skipped entirely.\n\n**Why**\n\nThis gives plugins a way to observe how each turn ended without adding overhead when no plugin cares about that information.\n\n- Area: Plugin Hooks\n- Names: `turn.complete`\n- Tier: Nothing to try yet\n- Useful: 4\/5\n- Signal: 3\/5"}