Managing provider credentials
Usebolt providers (aliased as bolt auth) to add, list, and remove provider credentials.
Add or update credentials
List configured providers
Remove credentials
Environment variable authentication
For CI pipelines or headless environments, set the provider’s API key environment variable directly — no interactive login required. Common examples:bolt providers list will surface which environment variables it detected.
Browsing available models
bolt models lists every model available across your configured providers.
Model identifier format
Models are always referenced inprovider/model format:
Selecting a model at runtime
--model / -m flag
The --model flag is available on bolt run, bolt commit, and bolt review:
--variant — controlling reasoning effort
Some models support configurable reasoning effort levels (e.g., Anthropic’s extended thinking, OpenAI’s reasoning models). Use --variant to select the effort tier:
The available variant values depend on the provider and model. Common values are
minimal, low, medium, high, and max, but the exact set varies. Check your provider’s documentation or use bolt models --verbose to see supported variants for a given model.--thinking — show reasoning blocks
When using a model that supports extended thinking, pass --thinking to surface the model’s chain-of-thought in the output:
Best-of-N parallel runs
--best-of fires the same prompt at multiple models in parallel, then uses a judge model to rank the responses and keep the best one:
--model, or to the first entry in the --best-of list if --model is not set. The flag accepts a comma-separated list of provider/model identifiers.
Arena — parallel runs in isolated worktrees
bolt arena takes the same idea further and races several agents on the same task. Each contender gets its own git worktree, so they can freely edit files without stepping on each other. When they finish, a judge model ranks them on the final answer plus the actual git diff — not just the text they wrote.
--best-of when the task involves editing files (refactors, feature work, test writing) rather than pure Q&A. The winning worktree stays on disk so you can inspect it, run tests, or merge the branch. The scoreboard and worktree paths print to stderr; the winner’s answer goes to stdout.
--modelsaccepts 2+provider/modelentries. Duplicates are allowed — racing a model against itself in separate worktrees is a legitimate setup.--judgepicks the ranking model (defaults to the first entry in--models).--cleanupdeletes losing worktrees and their branches after judging. Without it, every worktree sticks around for you to review.--format jsonemits a single JSON payload with the winner, ranking, and every candidate for scripting.
bolt arena in the command reference for the full flag list.