OMP Settings Demystified
The /settings screen, annotated. Click any line to see what it controls, its type and default, and
the exact key for ~/.omp/agent/config.yml. In panel view, clicking a tab inside the capture makes
the capture that tab. ⌘K searches every tab.
How a value is resolved
This reference shows the schema default. Anything below it in this list wins at runtime, so a value you see here can be overridden by config, flags, or environment.
- Schema defaulttyped built-in shown by this reference
- Global config
~/.omp/agent/config.yml - Project config
.omp/config.ymlin the current working directory - CLI overlays
--configfiles, applied in order - Runtime overridesdedicated flags and feature-specific environment variables
/settings and omp config set write global config only.
Project config is edited by hand. Environment variables are feature-specific, not one uniform layer.
Descriptions and defaults come from the OMP schema. Clearly marked editorial guidance assumes a local development workflow and is not an OMP default.
Config-file only
Present in the schema, deliberately absent from the panel: numeric and list settings with no finite option set have no widget, so they are edited in YAML.
| Key | Type | Default | What it controls |
|---|