Skip to main content
Gimorra runs its agents on a coding-agent engine, the Claude Code SDK by default, which uses the Anthropic Messages API. You choose the model and the endpoint that serves it. Pick one of the setups below, then verify the connection. Gimorra reads settings from two places. An environment variable overrides the config file, and the config file overrides the built-in default:

Pick a setup

If the Claude Code CLI is logged in on this machine, you don’t need to configure anything. When no endpoint, key or model is set, Gimorra uses that login.To set it explicitly and choose the model:
To use the login for one run without changing the default:
In a Claude Code cloud session, the shell already has the session’s Claude settings, and Gimorra’s runs use them.

Example: a main lane with a standby behind it

This is a real-world setup: one proxy, two fast models doing the work, and a stronger model on each lane for when a fast one stumbles. Drop it in your shell profile and every run picks it up:
When a session keeps failing, it walks down this ladder instead of failing the run:
The ladder tries the same endpoint with its _MODEL_FALLBACK first, because swapping models is a smaller change than swapping providers. That step alone often clears a model-level 429 or an “overloaded” error. When _MODEL_FALLBACK is a model Gimorra knows costs less, cheap-tier child agents also run on it, while the supervisor and the attack sessions keep the main model. Each connection has its own prefix. Declare as many as you have relays, and the ladder walks only the ones you set, in this order: Then prove every rung answers before you start a scan:

Save the settings in the config file

Each GIMORRA_LLM_* variable has a matching key under the main connection. gimorra config set saves the value in ~/.gimorra/configs.yaml, with file mode 0600:
main is the default connection. The supervisor, its child agents and every phase use it, unless a routing rule sends them somewhere else.

Verify the connection

gimorra config llm shows the settings Gimorra resolved. gimorra doctor llm tests them by sending one 16-token request to each model:
Run gimorra doctor llm after every change. If it passes, a run can reach the model.

Route work to different models

You can add more connections and send different work to each one. For example, the supervisor can use a strong model while the child agents use a cheaper one. Add the connections to ~/.gimorra/configs.yaml:
To use a connection for one run, pass --llm-profile, or -L for short:
Gimorra checks routing rules in a fixed order and uses the first match: planning, profiles, kinds, tiers, engines, and then the default.

When a provider fails

By default, llm.routing.on_failure is chain. When a session keeps failing on one connection, Gimorra moves it down the fallback ladder instead of failing the run. llm.routing.retry_budget_ms limits the total time one session spends retrying, and the default is 2 hours. Set on_failure to off if you want a session to fail as soon as its connection runs out of retries.

Reasoning effort

--llm-effort <level>, or -E, sets the model’s reasoning effort for one run. To change it on a run that is already going:
Gimorra spends tokens on your account. Every run has a spend limit. See Budgets and limits.