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.
Omarchy Core ISO
Reported by e0 · filed Sep 25, 2025Closed upstream on 2025-09-25 by ryanrhughes. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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?
- Not yet mapped to any requirement or component.
- 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. No decision has been recorded yet.
Original report
What do you need?
I propose that we add a lighter version of Omarchy ISO.
The goals are:
- maintain curation of defaults that includes everything essential to the core Omarchy experience
- reduce post-install setup time for new users: installling is faster than deleting+installing
- smaller install size and faster install time
From looking through the manual, the following are my lists of essentials (should be a part of Omarchy Core ISO) and optionals (should be excluded).
Essentials:
- Neovim
- All shell tools and functions
- TUIs
- Lazygit
- Btop
- Impala
- Fastfetch
- Development tools
- Alacritty
- Environment
- Mise
- Anything else that's not mentioned under Optionals
Optionals:
- TUIS
- Lazydocker
- All GUIs
- All commercial GUIs
- Development tools
- Environments except the Mise manager (Ruby on Rails, JavaScript runtimes, PHP frameworks etc)
- Docker
- GitHub CLI
- Filling out PDFs
- Document Viewer
- Xournal++
- All web apps
- All gaming apps (Steam, RetroArch, Minecraft)
Of course, these are up for debate, I thought about having some of the GUIs as good defaults, but that's too subjective, which is the whole point of this issue. Since it's already so easy to install apps, I think having a smaller ISO like this will offer a much more streamlined setup experience while keeping the best of what Omarchy offers.
View raw text
### What do you need?
I propose that we add a lighter version of Omarchy ISO.
The goals are:
- maintain curation of defaults that includes everything essential to the core Omarchy experience
- reduce post-install setup time for new users: installling is faster than deleting+installing
- smaller install size and faster install time
From looking through the manual, the following are my lists of essentials (should be a part of Omarchy Core ISO) and optionals (should be excluded).
Essentials:
- Neovim
- All shell tools and functions
- TUIs
- Lazygit
- Btop
- Impala
- Fastfetch
- Development tools
- Alacritty
- Environment
- Mise
- Anything else that's not mentioned under Optionals
Optionals:
- TUIS
- Lazydocker
- All GUIs
- All commercial GUIs
- Development tools
- Environments except the Mise manager (Ruby on Rails, JavaScript runtimes, PHP frameworks etc)
- Docker
- GitHub CLI
- Filling out PDFs
- Document Viewer
- Xournal++
- All web apps
- All gaming apps (Steam, RetroArch, Minecraft)
Of course, these are up for debate, I thought about having some of the GUIs as good defaults, but that's too subjective, which is the whole point of this issue. Since it's already so easy to install apps, I think having a smaller ISO like this will offer a much more streamlined setup experience while keeping the best of what Omarchy offers.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.
No decision has been recorded yet.