{"version":"2.1.283","anchor":"agent-tool-usage-totals-come-from-the-last-metered-assistant","canonical_anchor":"agent-tool-usage-totals-come-from-the-last-metered-assistant","heading":"Subagent and workflow token counts skip unmetered messages","tier":"notice","area":"Subagents","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/agent-tool-usage-totals-come-from-the-last-metered-assistant","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Subagent and workflow token counts skip unmetered messages\n\nSubagent progress, subagent totals and workflow agent counts now ignore usage from assistant messages marked isUnmetered\n\n**What**\n\nA subagent is a helper Claude starts to work on part of a task. Some of Claude's messages are now marked `isUnmetered`, meaning they are not counted as billed usage. Token counts now leave those messages out:\n\n- Subagent results: the usage and `total_tokens` reported when a subagent finishes now come from the last assistant message not marked `isUnmetered`, instead of the final message.\n\n- Subagent progress: the line showing tool-use count and tokens while a subagent runs now takes usage from the last message not marked `isUnmetered`.\n\n- Workflow agents: in workflow `agent()` runs, both the running token count and the final count skip usage from messages marked `isUnmetered`.\n\n**Why**\n\nToken numbers for subagents and workflows should reflect billed usage, and the counter should no longer jump or drop to zero when an unmetered message happens to be the last one.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}