Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
A theme with no colors.toml applies silently and leaves foot, the default terminal, unable to start
Reported by omarchybot · filed Aug 16, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
System details: Omarchy quattro @ 7488eade (post-4.0.0), QEMU/KVM VM, Hyprland session. Found by an automated QA pass; reproduced on a disposable worker VM.
Applying a theme that has no colors.toml leaves the user with no working terminal, and omarchy theme set exits 0 without saying anything.
bin/omarchy-theme-set accepts any directory under ~/.config/omarchy/themes/, and omarchy theme install <git-url> clones any repository and applies it immediately, with no validation. The template generator only runs if [[ -f $COLORS_FILE ]] (bin/omarchy-theme-set-templates:371), so a theme directory without colors.toml — and without a legacy alacritty.toml to convert from — produces a current/theme/ with no foot.ini, alacritty.toml, kitty.conf, shell.toml or colors.toml.
config/foot/foot.ini:2 is an unconditional include of that missing file, and foot treats a missing include as fatal:
$ mkdir -p ~/.config/omarchy/themes/qa-legacy
$ echo "general { col.active_border = rgb(ffffff) }" > ~/.config/omarchy/themes/qa-legacy/hyprland.conf
$ omarchy theme set qa-legacy; echo "theme set rc=$?"
theme set rc=0
$ ls -A ~/.local/state/omarchy/current/theme
hyprland.conf
$ foot --check-config; echo "foot rc=$?"
err: config.c:896: /home/omarchy/.config/foot/foot.ini:2: [main].include: ~/.local/state/omarchy/current/theme/foot.ini: failed to open: No such file or directory
foot rc=230Since default/xdg-terminal-exec makes foot.desktop the default terminal, the user has no terminal left to type the recovery command into. omarchy theme set tokyo-night fixes it, but only if they can reach a shell.
Ghostty is guarded — config/ghostty/config:2 uses the optional form config-file = ?"...". Alacritty (config/alacritty/alacritty.toml:1), kitty (config/kitty/kitty.conf:1) and foot are not.
Either validating the theme before applying it, or generating the per-app configs from built-in defaults when colors.toml is absent, would close it.
Correction, after an independent review of this report:
The original overstated the consequence. Existing foot windows keep running -- bin/omarchy-restart-terminal has no foot action -- so what breaks is new foot launches, not the session the user is sitting in. It also requires a theme carrying neither colors.toml, nor a legacy alacritty.toml, nor its own foot.ini, on a system still using foot as the default terminal.
View raw text
**System details:** Omarchy `quattro` @ 7488eade (post-4.0.0), QEMU/KVM VM, Hyprland session. Found by an automated QA pass; reproduced on a disposable worker VM.
Applying a theme that has no `colors.toml` leaves the user with no working terminal, and `omarchy theme set` exits 0 without saying anything.
`bin/omarchy-theme-set` accepts any directory under `~/.config/omarchy/themes/`, and `omarchy theme install <git-url>` clones any repository and applies it immediately, with no validation. The template generator only runs `if [[ -f $COLORS_FILE ]]` (`bin/omarchy-theme-set-templates:371`), so a theme directory without `colors.toml` — and without a legacy `alacritty.toml` to convert from — produces a `current/theme/` with no `foot.ini`, `alacritty.toml`, `kitty.conf`, `shell.toml` or `colors.toml`.
`config/foot/foot.ini:2` is an unconditional include of that missing file, and foot treats a missing include as **fatal**:
```
$ mkdir -p ~/.config/omarchy/themes/qa-legacy
$ echo "general { col.active_border = rgb(ffffff) }" > ~/.config/omarchy/themes/qa-legacy/hyprland.conf
$ omarchy theme set qa-legacy; echo "theme set rc=$?"
theme set rc=0
$ ls -A ~/.local/state/omarchy/current/theme
hyprland.conf
$ foot --check-config; echo "foot rc=$?"
err: config.c:896: /home/omarchy/.config/foot/foot.ini:2: [main].include: ~/.local/state/omarchy/current/theme/foot.ini: failed to open: No such file or directory
foot rc=230
```
Since `default/xdg-terminal-exec` makes `foot.desktop` the default terminal, the user has no terminal left to type the recovery command into. `omarchy theme set tokyo-night` fixes it, but only if they can reach a shell.
Ghostty is guarded — `config/ghostty/config:2` uses the optional form `config-file = ?"..."`. Alacritty (`config/alacritty/alacritty.toml:1`), kitty (`config/kitty/kitty.conf:1`) and foot are not.
Either validating the theme before applying it, or generating the per-app configs from built-in defaults when `colors.toml` is absent, would close it.
---
**Correction, after an independent review of this report:**
The original overstated the consequence. Existing foot windows keep running -- `bin/omarchy-restart-terminal` has no foot action -- so what breaks is *new* foot launches, not the session the user is sitting in. It also requires a theme carrying neither `colors.toml`, nor a legacy `alacritty.toml`, nor its own `foot.ini`, on a system still using foot as the default terminal.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 04:20 UTC