{"version":"2.1.267","anchor":"plugin-event-schema-gains-a-usage-field-on-turnstep-and-t","canonical_anchor":"plugin-event-schema-gains-a-usage-field-on-turnstep-and-t","heading":"Turn events now include token usage data","tier":"use","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/plugin-event-schema-gains-a-usage-field-on-turnstep-and-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Turn events now include token usage data\n\nturn.step and turn.complete events, including plugin hooks, now carry token usage information\n\n**What**\n\n- The `turn.complete` event payload now includes a computed usage object when available, alongside the existing `answer`, `durationMs`, `aborted`, and `turnId` fields.\n\n- The `turn.step` and `turn.complete` telemetry event payloads now include a `usage` field whenever the underlying event carries usage data.\n\n- 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.step` and `turn.complete` events, pulled from the assistant message.\n\n**Why**\n\nPlugins, 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.\n\n- Area: Hooks\n- Names: `usage`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}