Skip to content

Replace run --budget with a general --config-override <yaml> flag#13

Merged
hbrooks merged 1 commit into
mainfrom
cli-config-override-flag
Jun 28, 2026
Merged

Replace run --budget with a general --config-override <yaml> flag#13
hbrooks merged 1 commit into
mainfrom
cli-config-override-flag

Conversation

@hbrooks

@hbrooks hbrooks commented Jun 28, 2026

Copy link
Copy Markdown
Member

Why

Follow-up to #12. That PR kept the -b, --budget <usd> convenience flag (translating it to a limits.run override). Per feedback, drop --budget entirely and expose the override mechanism directly.

What changed

  • Removed -b, --budget <usd>.
  • Added -o, --config-override <yaml>: a partial agent config merged onto the chosen config and re-validated server-side. Set limits.run to override this run's budget; any other config field works too.
  • req.config_override_yaml is now set straight from the flag (no client-side YAML construction).
  • README: replaced the implicit budget example with a --config-override example.
agent run start --config <id> --config-override "limits:\n  run: 5"

Testing

  • npm run typecheck, npm run test (89), npm run build all pass.

🤖 Generated with Claude Code

Drop the -b, --budget convenience flag. Expose the full config-override mechanism directly: -o, --config-override <yaml> is a partial agent config merged onto the chosen config and re-validated server-side (set limits.run to override the budget). README updated.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@hbrooks hbrooks merged commit 7dd2338 into main Jun 28, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant