Workflow agents that blow past their token ceiling are now stopped, with a log line telling you how to raise it.
What's wrong with this entry?
In 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.
- Token spend is checked as the agent reports usage; on breach an
over-budgetfact is published carrying the label, the agent, the amount spent and the ceiling. - The agent's row is retracted at the same time.
- Previously the only similar state was
starved, which covers agents waiting on something rather than agents overspending. - No flag guards this; it applies wherever the Workflow v2 tools are in use.
; put {topic:'budget', units:N} to raise the ceiling
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.239
Workflow tool gains run operations, with the auto-approval hook switched off
Both mention workflow
-
v2.1.239
Workflow tool has a second command shape built in but switched off
Both mention workflow
-
v2.1.239
Workflow "v2 run" handles are scaffolded but never created
Both mention workflow