What
Claude 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.
Why
This gives plugins a way to observe how each turn ended without adding overhead when no plugin cares about that information.
Names in the bundleturn.complete
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 turn.complete, on React to events with a mod.
A turn is everything Claude does in answer to one prompt. Handle `turn.start`, `turn.step`, and `turn.complete` to follow one:plugins/mods/events see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up turn.complete, on React to events with a mod.