When aDocumentation Index
Fetch the complete documentation index at: https://docs.praison.ai/llms.txt
Use this file to discover all available pages before exploring further.
praisonai CLI run goes over its budget, you get a clean error message and exit-code 1 — no Python traceback.
Quick Start
How It Works
Thepraisonai CLI wraps every agent.start(...) / agent.chat(...) call in a budget handler. When the agent raises BudgetExceededError, the CLI:
- Prints a single-line, red, rich-formatted message including the actionable hint.
- Exits with code
1so shell scripts and CI can detect the failure.
silent (-qq), quiet (-q), verbose (-v), debug (-vv), --output jsonl, --output json, --output flow, --output editor, and default.
Using the Exit Code in CI / Scripts
| Exit code | Meaning |
|---|---|
0 | Success |
1 | BudgetExceededError (or other handled fatal error) |
Why isn’t there a max_budget= shortcut on Agent?
By design. Per AGENTS.md §5.3 (Parameter Consolidation), execution-related knobs live on ExecutionConfig, not as new top-level Agent.__init__ parameters. This keeps the Agent constructor small and discoverable. The CLI’s error message points users to the one correct place to set a budget:
Catching the error in your own code
If you embedpraisonaiagents directly (not via the CLI), you can catch the same exception:
Best Practices
Set a budget cap early
Set a budget cap early
Without
max_budget, a runaway agent can rack up costs unbounded. Pick a cap based on a few un-budgeted dev runs.Use the exit code in automation
Use the exit code in automation
The graceful exit means CI detects the failure cleanly — no need to grep tracebacks.
Don't look for a top-level max_budget= on Agent
Don't look for a top-level max_budget= on Agent
There isn’t one. Use
execution=ExecutionConfig(max_budget=...) — that’s the only supported pattern.Related
Budget Management
Full SDK API for budgets, cost tracking, and
on_budget_exceeded actionsExecution Configuration
All execution settings including retries, timeouts, and rate limits

