otter-settings is the main config UI. One tab per app, a theme browser, and drag-and-drop bar layout. It writes the same ~/.config/otter-shell/*.conf files you would edit by hand, so the GUI and text stay in sync.
Click Apply and most running apps reload via inotify. No restart needed.
What you can configure in otter-settings
Compositor hotkeys (screenshot, launcher, overview, lock) are not in otter-settings. Bind those in your compositor config. See Keybinds.
Manual config files
Each app has a plain-text file in~/.config/otter-shell/. Edit by hand when you want to script changes, or keep comments the UI might not show.
System defaults may live under
/etc/otter-shell/. User configs always win.
File format
true or false. Empty string "" falls back to the compiled default.
On first launch, apps normalize their config: missing keys get defaults, unknown keys are removed.
Hot reload
Most daemons watch their config (and oftentheme.conf) with inotify:
- otter-bar: reloads
otter-bar.confon save;theme.confchanges refresh widget colors without a full bar config reload - otter-notifications, otter-wallpaper, otter-osd, otter-idle: reload on save
- otter-term: hot-reloads
otter-term.confand sharedtheme.conf - otter-monitor: hot-reloads
theme.confonly; restart to pick upotter-monitor.confchanges - otter-transcribe: reloads settings and watches
theme.conf; restarts automatically after a model unload when idle
System-wide defaults
Lookup order (example forotter-term):
~/.config/otter-shell/otter-term.conf(user: highest priority)/etc/otter-shell/otter-term.conf(system defaults)- Compiled-in defaults
/etc/otter-shell/ without touching home directories.
