Nothing to try yet Notable
No documentation found
A new turn.complete hook reports a turn's final answer, refusal, usage and error state, but only when a plugin listens for it
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