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.5 broke the terminal keybind
Reported by abarchin · filed Nov 5, 2025Closed upstream on 2025-11-05 by its own reporter abarchin, as a duplicate of #3176 (R-3655). GitHub close reason: duplicate.
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
Thinkpad P53 Xeon E-2276M, Nvidia Quadro RTX 5000, Omarchy 3.1.5
What's wrong?
Last Omarchy 3.1.5 update broke the keybind for opening a new terminal. This line does not work:
bindd = SUPER, RETURN, Terminal, exec, $terminal --working-directory $(omarchy-cmd-terminal-cwd)
Managed to fix it by removing the arguments and leaving it as just:
bindd = SUPER, RETURN, Terminal, exec, $terminal
View raw text
### System details Thinkpad P53 Xeon E-2276M, Nvidia Quadro RTX 5000, Omarchy 3.1.5 ### What's wrong? Last Omarchy 3.1.5 update broke the keybind for opening a new terminal. This line does not work: `bindd = SUPER, RETURN, Terminal, exec, $terminal --working-directory $(omarchy-cmd-terminal-cwd)` Managed to fix it by removing the arguments and leaving it as just: `bindd = SUPER, RETURN, Terminal, exec, $terminal`
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.