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.
3.1.0 and 3.1.1 - New keybindings missing, Walker styling and broken Omarchy menu options
Reported by rCirelli · filed Oct 23, 2025Closed upstream on 2025-10-23 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
System details
Omarchy 3.1.1
What's wrong?
Hey guys, I had a few issues with the two latest updates.
Just to contextualize, on the 3.1.0 update, apparently it was supposed to have an op-in to enable new keybindings. When I updated, there was no opt-in, and none of the changes were made available to me. Not a big deal, I was just going to wait the next releases and see if the changes would eventually be available to me.
But then 3.1.1 came out, I updated. Still no new keybindings, but had issues with walker and Omarchy menu.
The Omarchy styling would be gone, the apps list would not load at all, making it impossible to launch an app that doesn't have a keybinding.
<img width="1916" height="1075" alt="Image" src="https://github.com/user-attachments/assets/a5bde3b8-d5f3-4d9c-b9f7-a78d57644a1c" />
Also, the omarchy menu would be kind of broken, a few options would not work.
<img width="1918" height="1078" alt="Image" src="https://github.com/user-attachments/assets/92f1cd53-7e4f-4759-a3a5-06711dc8d571" />
I couldn't screen-record for some reason, but basically every option in the omarchy menu bellow "Style" just goes to the "Style" menu.
Because of these issues I rolled back to 3.1.0 (still without the new keybindings and features like tiling groups).
(edit: added screenshot of the broken omarchy menu)
View raw text
### System details Omarchy 3.1.1 ### What's wrong? Hey guys, I had a few issues with the two latest updates. Just to contextualize, on the 3.1.0 update, apparently it was supposed to have an op-in to enable new keybindings. When I updated, there was no opt-in, and none of the changes were made available to me. Not a big deal, I was just going to wait the next releases and see if the changes would eventually be available to me. But then 3.1.1 came out, I updated. Still no new keybindings, but had issues with walker and Omarchy menu. The Omarchy styling would be gone, the apps list would not load at all, making it impossible to launch an app that doesn't have a keybinding. <img width="1916" height="1075" alt="Image" src="https://github.com/user-attachments/assets/a5bde3b8-d5f3-4d9c-b9f7-a78d57644a1c" /> Also, the omarchy menu would be kind of broken, a few options would not work. <img width="1918" height="1078" alt="Image" src="https://github.com/user-attachments/assets/92f1cd53-7e4f-4759-a3a5-06711dc8d571" /> I couldn't screen-record for some reason, but basically every option in the omarchy menu bellow "Style" just goes to the "Style" menu. Because of these issues I rolled back to 3.1.0 (still without the new keybindings and features like tiling groups). (edit: added screenshot of the broken omarchy menu)
- a5bde3b8-d5f3-4d9c-b9f7-a78d57644a1c
- 92f1cd53-7e4f-4759-a3a5-06711dc8d571
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.