fix(config): preserve explicit custom provider against legacy PROVIDER override
This commit is contained in:
parent
d6dca4b890
commit
9381e4451a
3 changed files with 67 additions and 4 deletions
|
|
@ -20,6 +20,19 @@ Schema export command:
|
|||
| `default_model` | `anthropic/claude-sonnet-4-6` | model routed through selected provider |
|
||||
| `default_temperature` | `0.7` | model temperature |
|
||||
|
||||
## Environment Provider Overrides
|
||||
|
||||
Provider selection can also be controlled by environment variables. Precedence is:
|
||||
|
||||
1. `ZEROCLAW_PROVIDER` (explicit override, always wins when non-empty)
|
||||
2. `PROVIDER` (legacy fallback, only applied when config provider is unset or still `openrouter`)
|
||||
3. `default_provider` in `config.toml`
|
||||
|
||||
Operational note for container users:
|
||||
|
||||
- If your `config.toml` sets an explicit custom provider like `custom:https://.../v1`, a default `PROVIDER=openrouter` from Docker/container env will no longer replace it.
|
||||
- Use `ZEROCLAW_PROVIDER` when you intentionally want runtime env to override a non-default configured provider.
|
||||
|
||||
## `[agent]`
|
||||
|
||||
| Key | Default | Purpose |
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue