Repository navigation
v0.10.3
Features
- Token budget (#246, part of #236):
--token-limit n/ configtoken_limitcaps provider-reported input+output tokens for the whole run. At the limit the run stops cleanly with the new statusTokenLimitExceeded(exit 1, resumable; the printed--resumecommand doubles the limit). Delegates and workers get only the tokens left in the parent's budget, and a worker batch shares one token gate. Off by default (0 = unlimited). - 80% budget warning (#246): when a token or cost budget reaches 80%, one "Budget notice" user message is added before the next request and a
budget.warningevent goes to the JSON stream, log DB and OTel trace. - Token limit everywhere (#247, closes #236):
--checkshows the token limit on the limits line,--init-configincludes a commentedtoken_limit: 0,--evalsuite tasks acceptlimits.token_limit, and--workflowacceptstoken_limitindefaultsand per stage.
Changes
- Behavior change for
--attempts(#247):--token-limitis now one budget shared by all attempts, like--cost-limitand--time-limit. Each attempt gets the tokens left, no new attempt starts once the budget is spent, and an attempt endingTokenLimitExceededstops the run withbudget exhausted. Previously each attempt got the full limit. - The turn cap (
--step-limit) stays off by default. A top-level--token-limitwith--evalis still a per-trial cap.
What's Changed
- Part of #236: token budget and budget warning by @vicgupta in #246
- Fix #236: show token limit in --check/init-config and forward it through eval, attempts and workflows by @vicgupta in #247
- Release v0.10.3 by @vicgupta in #248
Full Changelog: v0.10.2...v0.10.3