Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-812GitHub issuePublicDecided· Out of scope

Theming docs don't warn that fonts and bar position are global, not theme-scoped

Reported by lucasvidela94 · filed Sep 8, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 days ago.

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

Theming docs don't warn that fonts and bar position are global, not theme-scopedrevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

AMD Ryzen 5 3450U with Radeon Vega Mobile Gfx (Picasso/Raven 2), Omarchy 4.0.2-1

What's wrong?

The theming documentation presents omarchy font set and bar layout as part of theming, but both are global user settings that persist across theme switches — a theme cannot scope them. This misled me into changing global state while building a custom theme, and the changes then leaked into every other theme.

Steps to recreate:

  1. Create a custom theme in ~/.config/omarchy/themes/<name>/ per docs/theming.md / the bundled skill default/agents/skills/omarchy/theming.md ("Fonts" section).
  2. Run omarchy font set Selawik, expecting it to apply only to the new theme.
  3. Switch back to the previous theme — the font change persists globally:
  • ~/.config/fontconfig/fonts.conf gets a monospace → <font> override that hijacks the packaged 50-omarchy.conf default (JetBrainsMono Nerd Font).
  • All four terminal configs are rewritten (alacritty.toml, kitty.conf, ghostty/config, foot.ini).
  1. The same applies to bar position in ~/.config/omarchy/shell.json: global, and it changes the bar for every theme.

Expected: the theming docs clearly separate theme-scoped config (colors.toml, shell.toml, icons.theme, backgrounds/) from global user settings (fonts via omarchy font set, bar position/layout in shell.json), with an explicit warning that a theme must not (and cannot) change those. A short "What a theme can and cannot scope" section would have prevented this.

Sources reviewed:
- docs/theming.md — no font or bar-scope guidance.
- default/agents/skills/omarchy/theming.md — lists fonts under theming without a global-scope warning.

View raw text
## System details
AMD Ryzen 5 3450U with Radeon Vega Mobile Gfx (Picasso/Raven 2), Omarchy 4.0.2-1

## What's wrong?

The theming documentation presents `omarchy font set` and bar layout as part of theming, but both are **global user settings** that persist across theme switches — a theme cannot scope them. This misled me into changing global state while building a custom theme, and the changes then leaked into every other theme.

Steps to recreate:

1. Create a custom theme in `~/.config/omarchy/themes/<name>/` per `docs/theming.md` / the bundled skill `default/agents/skills/omarchy/theming.md` ("Fonts" section).
2. Run `omarchy font set Selawik`, expecting it to apply only to the new theme.
3. Switch back to the previous theme — the font change persists globally:
   - `~/.config/fontconfig/fonts.conf` gets a `monospace → <font>` override that hijacks the packaged `50-omarchy.conf` default (JetBrainsMono Nerd Font).
   - All four terminal configs are rewritten (`alacritty.toml`, `kitty.conf`, `ghostty/config`, `foot.ini`).
4. The same applies to bar `position` in `~/.config/omarchy/shell.json`: global, and it changes the bar for every theme.

Expected: the theming docs clearly separate **theme-scoped** config (`colors.toml`, `shell.toml`, `icons.theme`, `backgrounds/`) from **global user settings** (fonts via `omarchy font set`, bar position/layout in `shell.json`), with an explicit warning that a theme must not (and cannot) change those. A short "What a theme can and cannot scope" section would have prevented this.

Sources reviewed:
- `docs/theming.md` — no font or bar-scope guidance.
- `default/agents/skills/omarchy/theming.md` — lists fonts under theming without a global-scope warning.

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 11:13 UTC