{"version":"2.1.295","anchor":"workflow-runs-have-no-token-budget","canonical_anchor":"workflow-runs-have-no-token-budget","heading":"Workflow runs no longer get a token budget total","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/workflow-runs-have-no-token-budget","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Workflow runs no longer get a token budget total\n\nThe token budget given to workflow runs no longer has a total; before, the total was worked out from the session's token count\n\n**Unclear.** It is not clear whether an empty total means workflow runs are now unlimited or are limited some other way.\n\n**What**\n\nTokens are the units Claude Code uses to measure how much text a model reads and writes. Workflow runs used to be given a token budget whose total was worked out from the session's token count. A session is one continuous conversation with Claude Code. That total is now left empty, while the run still tracks how many tokens each turn spends.\n\n**Why**\n\nWithout a total, workflow runs no longer carry a token limit taken from the session. If you relied on that limit to keep workflow runs short, keep an eye on how much they use.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}