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.
File Manager is not a Defaults category (hardcoded to Nautilus, ignores xdg-mime)
Reported by mrocha-montes · filed Sep 6, 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?
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. So far: partly in the audited area (menu) — decided by agents · verified; not a duplicate of another report — decided by agents · verified. The outcome (valid, duplicate, not a bug, …) is not decided yet. See the decision.
Original report
Browser, Terminal, Editor and Agent all have a proper category under Setup > Defaults: a menu entry, a dynamic launcher script that resolves the current choice, and an omarchy-default-<category> setter. File Manager does not.
omarchy-launch-nautilus (bound to SUPER+E by default) is hardcoded:
exec setsid uwsm-app -- nautilus --new-windowCompare with omarchy-launch-browser, which reads xdg-settings get default-web-browser, resolves the Exec= line from the matching .desktop file, and launches that. File managers already follow the equivalent freedesktop standard (xdg-mime query default inode/directory), so the same pattern would work with no new spec to invent.
Concretely: if I install Dolphin (or Thunar, Nemo, PCManFM...) and set it as my default via xdg-mime default org.kde.dolphin.desktop inode/directory, SUPER+E still opens Nautilus regardless. The keybind is wired to a specific app instead of "whatever the user's default file manager is."
Suggested fix, mirroring the existing browser pattern:
- omarchy-launch-filemanager: resolve xdg-mime query default inode/directory, extract Exec=, launch it.
- omarchy-default-filemanager <id>: wrapper around xdg-mime default <desktop-id> inode/directory, for a fixed list of common file managers (nautilus, dolphin, thunar, nemo, pcmanfm, etc).
- setup.default.filemanager.* entries in omarchy-menu.jsonc, same shape as setup.default.browser.*.
- Point the default SUPER+E binding at { omarchy = "filemanager" } instead of { omarchy = "nautilus" }.
Happy to submit a PR with this if it's a welcome direction.
View raw text
Browser, Terminal, Editor and Agent all have a proper category under Setup > Defaults: a menu entry, a dynamic launcher script that resolves the current choice, and an `omarchy-default-<category>` setter. File Manager does not.
`omarchy-launch-nautilus` (bound to SUPER+E by default) is hardcoded:
```bash
exec setsid uwsm-app -- nautilus --new-window
```
Compare with `omarchy-launch-browser`, which reads `xdg-settings get default-web-browser`, resolves the `Exec=` line from the matching `.desktop` file, and launches that. File managers already follow the equivalent freedesktop standard (`xdg-mime query default inode/directory`), so the same pattern would work with no new spec to invent.
Concretely: if I install Dolphin (or Thunar, Nemo, PCManFM...) and set it as my default via `xdg-mime default org.kde.dolphin.desktop inode/directory`, SUPER+E still opens Nautilus regardless. The keybind is wired to a specific app instead of "whatever the user's default file manager is."
Suggested fix, mirroring the existing browser pattern:
- `omarchy-launch-filemanager`: resolve `xdg-mime query default inode/directory`, extract `Exec=`, launch it.
- `omarchy-default-filemanager <id>`: wrapper around `xdg-mime default <desktop-id> inode/directory`, for a fixed list of common file managers (nautilus, dolphin, thunar, nemo, pcmanfm, etc).
- `setup.default.filemanager.*` entries in `omarchy-menu.jsonc`, same shape as `setup.default.browser.*`.
- Point the default SUPER+E binding at `{ omarchy = "filemanager" }` instead of `{ omarchy = "nautilus" }`.
Happy to submit a PR with this if it's a welcome direction.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
- Fixed bypr/10542· confirmed
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.
- Decided by agents · verified: partly in the audited area (menu)
- Decided by agents · verified: not a duplicate of another report
The outcome (valid, duplicate, not a bug, …) is not decided yet.