Set useful task budgets
Put cost, tokens and time next to the scope of a task before the work grows.
Bound the work first
A budget is more useful when the task has a concrete result. Split open-ended exploration from implementation, and name the checks needed for each. This makes it easier to decide whether another attempt is worthwhile.
Use the supported controls
VECTA has task budget controls for cost, tokens and time. Availability depends on the connected runtime and runner version. Read the budget status shown by the task before relying on enforcement.
Leave room for reporting delays
Agents may report usage after a chunk of work has completed. A task budget is not a guarantee of an exact provider billing ceiling. Use provider-side spending controls too when you need an account-wide payment limit.