Configuration

Ódinn stores ordinary runtime configuration in the selected state directory. Prefer CLI and onboarding commands to hand-editing the configuration file; they validate values, preserve unrelated state, and show dangerous-impact summaries.

State selection

Most commands accept:

odinn <command> --state <directory>

Without an explicit path, Ódinn uses a detected project state or the user’s default state directory.

Providers and models

odinn config provider catalog
odinn config provider list
odinn config provider remove <name>
odinn config model list
odinn config model default <provider:model>

Provider secrets stay outside ordinary configuration. API-key providers reference an environment-variable name; OAuth material lives in the private OAuth store.

Security

odinn config security show

Security surfaces include web and browser access, private-network access, domain rules, and browser-action approval. Changes that broaden authority require explicit impact confirmation.

Labs

odinn experimental status
odinn experimental enable proof --confirm-impact
odinn experimental disable proof

The seven feature flags are independent and false by default. Restart a running gateway after a gate change.

Automatic improvements

odinn config self-improvement show
odinn config self-improvement set \
  --enabled true \
  --mode auto \
  --interval-ms 300000 \
  --max-changes 1

Supported modes are disabled, propose, and auto. The v0.4.0-beta.3 default is enabled auto mode with one bounded change per cycle and rollback on failure.

Configuration discipline

• Back up state before manual changes.
• Do not place credentials in configuration.
• Preserve custom policy unless intentionally replacing it.
• Verify a provider after changing it.
• Restart the gateway when startup configuration changes.
• Use odinn doctor after repair or restore.

For store locations, see State layout.