Group of 3 Use it now
turn.step and turn.complete events, including plugin hooks, now carry token usage information
What
- The
turn.completeevent payload now includes a computed usage object when available, alongside the existinganswer,durationMs,aborted, andturnIdfields. - The
turn.stepandturn.completetelemetry event payloads now include ausagefield whenever the underlying event carries usage data. - The plugin/hooks event-summary logger now includes token usage details (input tokens, output tokens, cache-read tokens, cache-creation tokens, and the model name) on
turn.stepandturn.completeevents, pulled from the assistant message.
Why
Plugins, hooks, and telemetry consumers can now see how many tokens a turn used directly from the turn events, without needing a separate lookup, which helps with cost tracking and observability.
Names in the bundleusage
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.
Added since
A small documentation edit on Legal and compliance touched a line naming usage after this was published.
An organization managed from the Enterprise Admin Console can also turn on usage analytics. Users' apps then report session, token, and estimated-cost counts to Anthropic, and the organization's administrators can see each user's sessions,…third-party/claude-desktop/legal see the edit
Confirmed since
Anthropic's documentation has since written up usage, on Keep Claude working toward a goal.
* **Pause**: after a failure that a retry would only repeat, such as an API rate limit, a claude.ai [usage limit](/docs/en/errors#youve-hit-your-session-limit), or a hook that ended the turn, a notice starting with `Goal paused` names the …goal 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 usage, on Keep Claude working toward a goal.