{"version":"2.1.246","anchor":"workflow-agent-token-usage-is-now-attributed-as-it-arrives","canonical_anchor":"workflow-agent-token-usage-is-now-attributed-as-it-arrives","heading":"Workflow agent token usage is now attributed as it arrives","tier":"internal","area":"Cost Tracking","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/workflow-agent-token-usage-is-now-attributed-as-it-arrives","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Workflow agent token usage is now attributed as it arrives\n\nWorkflow agent token use is charged as it arrives instead of being thrown away.\n\n**What**\n\nProgress updates from a workflow agent that carry a numeric token count are charged incrementally against that agent instead of being discarded, so per-agent spend adds up during the run.\n\n**Evidence**\n\n`workflow_agent`\n\n- Area: Cost Tracking\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}