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.
Need for explainer video series
Reported by ainslec · filed Sep 13, 2025Closed upstream on 2025-11-03. 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
Background
Professionally, I’ve spent much of my career in Linux land—mostly headless, server-side deployments. I still drop into vi when light editing is needed. Since Amiga I've always been on Windows as my desktop environment.
When I first tried Omarchy, I felt that spark of Euphoria. But the shine has worn off, and I’m mostly left with confusion. I keep going back to the long DHH video, hoping to pick up clues, but I still don’t feel in command of the system.
- Is the tiling manager meant to become borderline crowded/unusable once you pass two or three tiles on a 1080p?
- What’s the right way to work with one monitor? With two? Is ultrawide better than my current 3:2 display?
- When I enter settings, I’m dropped into a completely foreign text editor with unknown keybindings. If I mess something up in there, what’s the damage? Where should I even be editing these configs?
- In Windows 10 I alt tab between full screened applications or click and icon at the bottom of the screen to go to that application. Windows 10 (and 11) are bloat, but frankly unless Omarchy "reveals itself unto thee", I'm not capable of seeing the light.
So - show me the light.
What correction or addition do we need?
I’d love to see a series of videos or blog posts on Omarchy best practices, including fly on the wall development stream, where key presses and features are verbalized as they are used - slow - repetitive. Something aimed at technical folks who may be seasoned developers but are new to Arch, and new to the default editor.
I was planning to make Omarchy my daily driver on a new Framework desktop, but after testing it on my ThinkPad, I realize I need more time to understand the mental model here. What assumptions are baked in about screen size and workspace usage?
This isn’t meant as a slight. I still think Omarchy has a big future. In fact, if it eventually shipped with a small optional AI model to answer these kinds of questions, that could be killer in a 3.x or 4.x release. But right now, as a forty-something dev, I honestly can’t tell whether I’m failing to adapt to a great design—or whether the design itself makes assumptions that just don’t fit me.
View raw text
### Background Professionally, I’ve spent much of my career in Linux land—mostly headless, server-side deployments. I still drop into vi when light editing is needed. Since Amiga I've always been on Windows as my desktop environment. When I first tried Omarchy, I felt that spark of Euphoria. But the shine has worn off, and I’m mostly left with confusion. I keep going back to the long DHH video, hoping to pick up clues, but I still don’t feel in command of the system. * Is the tiling manager meant to become borderline crowded/unusable once you pass two or three tiles on a 1080p? * What’s the right way to work with one monitor? With two? Is ultrawide better than my current 3:2 display? * When I enter settings, I’m dropped into a completely foreign text editor with unknown keybindings. If I mess something up in there, what’s the damage? Where should I even be editing these configs? * In Windows 10 I alt tab between full screened applications or click and icon at the bottom of the screen to go to that application. Windows 10 (and 11) are bloat, but frankly unless Omarchy "reveals itself unto thee", I'm not capable of seeing the light. So - show me the light. ### What correction or addition do we need? I’d love to see a series of videos or blog posts on Omarchy best practices, including fly on the wall development stream, where key presses and features are verbalized as they are used - slow - repetitive. Something aimed at technical folks who may be seasoned developers but are new to Arch, and new to the default editor. I was planning to make Omarchy my daily driver on a new Framework desktop, but after testing it on my ThinkPad, I realize I need more time to understand the mental model here. What assumptions are baked in about screen size and workspace usage? This isn’t meant as a slight. I still think Omarchy has a big future. In fact, if it eventually shipped with a small optional AI model to answer these kinds of questions, that could be killer in a 3.x or 4.x release. But right now, as a forty-something dev, I honestly can’t tell whether I’m failing to adapt to a great design—or whether the design itself makes assumptions that just don’t fit me.
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
- Related PRpr/12816· 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.
No decision has been recorded yet.