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.
[Feature Request] Use $mainMod instead of hardcoded SUPER
Reported by MatthewHunt84 · filed Aug 31, 2025Closed upstream on 2026-02-01 by dhh, as not planned.
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
Follow up to this issue closed earlier today.
I'm a longtime mac user (and linux newbie) who has been inspired to try out Omarchy after seeing the overwhelmingly positive community response to it. It's fast and beautiful and lives up to the hype! One thing I've noticed however, is that there seems to be no way to easily remap the SUPER functionality to a different key?
I've seen the common recommendation to use kb_options, but what I'm looking for is a way to move the SUPER functionality to another modifier and free up the SUPER key itself for other commands. For instance, I would love to be able to move the original SUPER functionality to a key like hyper. Once that's moved, I could use the SUPER key (command on mac) for other operations. In my case these operations would include copy, cut & paste (super-c / super-v, super-x) or jump to the start / end of lines (super-left, super-right) some of which currently conflict with other hyprland commands.
I know a request to make linux more like macOS is hilarious, and I agree that learning the Omarchy keybinds is generally the right move, however it seems like there is already a precedent for a $mainMod key in hyprland which looks like this:$mainMod = HYPER # or whatever
That would be a really nice feature for those of us who are new / constantly need to switch operating systems for work, etc.
View raw text
Follow up to [this issue](https://github.com/basecamp/omarchy/issues/1115) closed earlier today. I'm a longtime mac user (and linux newbie) who has been inspired to try out Omarchy after seeing the overwhelmingly positive community response to it. It's fast and beautiful and lives up to the hype! One thing I've noticed however, is that there seems to be no way to easily remap the SUPER functionality to a different key? I've seen the common recommendation to use kb_options, but what I'm looking for is a way to move the SUPER _functionality_ to another modifier and free up the SUPER key itself for other commands. For instance, I would love to be able to move the original SUPER functionality to a key like hyper. Once that's moved, I could use the SUPER key (command on mac) for other operations. In my case these operations would include copy, cut & paste (super-c / super-v, super-x) or jump to the start / end of lines (super-left, super-right) some of which currently conflict with other hyprland commands. I know a request to make linux more like macOS is hilarious, and I agree that learning the Omarchy keybinds is generally the right move, however it seems like there is already a precedent for a $mainMod key in hyprland which looks like this: `$mainMod = HYPER # or whatever` That would be a really nice feature for those of us who are new / constantly need to switch operating systems for work, etc.
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.