mirror of
https://github.com/fabro-sh/fabro.git
synced 2026-10-07 03:00:29 +00:00
b32164b086
A run can now carry an optional spend budget. New [run.limits] settings table with max_cost (USD) and max_tokens; when accumulated LLM spend exceeds either limit, the run halts immediately and fails with the existing BudgetExhausted failure reason. - RunBudget (fabro-model): thread-safe accumulator shared across the engine, agent sessions, hooks, and the prompt path. Charges per LLM response; queues one-shot 80% warnings drained into run notices. - Enforcement is inline at every usage-recording site: the agent turn loop (interrupting like the wall-clock timeout via a new InterruptReason::BudgetExhausted), subagent sessions, the one-shot prompt path with schema-repair retries, context compaction, web_fetch summarization, and prompt/agent hooks (which skip once the budget is spent, matching their fail-open posture). - Budget exhaustion terminates the run as an engine-level error (fabro_core::Error::BudgetExhausted, following the StallTimeout pattern) so fail edges are not followed, plus a between-stage gate for non-LLM stages and a run-start gate that makes a resumed budget-failed run fail fast until the limit is raised (spend is seeded from the billing projection). - Exposed on the RunNamespace OpenAPI schema (RunLimitsSettings); Rust and TypeScript clients regenerated; docs updated. Known gaps, by design for now: ACP external agents report no usable per-response usage (cumulative UsageUpdate capture is a follow-up), and post-run PR content generation is outside the engine. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| administration | ||
| agents | ||
| api-reference | ||
| changelog | ||
| core-concepts | ||
| examples | ||
| execution | ||
| getting-started | ||
| human-tools | ||
| images | ||
| integrations | ||
| languages | ||
| logo | ||
| reference | ||
| tutorials | ||
| workflows | ||
| .mintignore | ||
| docs.json | ||
| dot-highlight.js | ||
| favicon.svg | ||
