{"version":"2.1.247","anchor":"workflow-agents-are-cut-off-when-they-run-past-their-token-c","canonical_anchor":"workflow-agents-are-cut-off-when-they-run-past-their-token-c","heading":"Workflow agents are cut off when they run past their token ceiling","tier":"notice","area":"Workflows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/workflow-agents-are-cut-off-when-they-run-past-their-token-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Workflow agents are cut off when they run past their token ceiling\n\nWorkflow agents that blow past their token ceiling are now stopped, with a log line telling you how to raise it.\n\n**What**\n\nIn the Workflow v2 tool surface, an agent that spends more tokens than its scope allows is now stopped rather than left running. The log line tells you how to raise the ceiling.\n\n**Details**\n\n- Token spend is checked as the agent reports usage; on breach an `over-budget` fact is published carrying the label, the agent, the amount spent and the ceiling.\n- The agent's row is retracted at the same time.\n- Previously the only similar state was `starved`, which covers agents waiting on something rather than agents overspending.\n- No flag guards this; it applies wherever the Workflow v2 tools are in use.\n\n**Evidence**\n\n`; put {topic:'budget', units:N} to raise the ceiling`\n\n- Area: Workflows\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}