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.
Remove SUPER+grave from fcitx5 QuickPhrase before the Quake console bind ships (patch included)
Reported by prusso · filed Sep 18, 2026 · open at source
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?
- AreaOutside the audited area· Decided by agents · verified
- 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?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
Recommendation: drop QuickPhrase's Super+grave trigger. It's a niche
feature most users never touch; the console is a deliberate, carefully
built one (multiple PRs on sizing, centering, agent-seeding). Add this
file, same pattern Omarchy already uses for clipboard.conf:
config/fcitx5/conf/quickphrase.conf
----------------------------------------
TriggerKey=
That's it. It's the identical override style already shipping today in
config/fcitx5/conf/clipboard.conf:
TriggerKey=
PastePrimaryKey=
which blanks a default fcitx5 trigger the same way. Copy the pattern,
new file, one line, done. QuickPhrase itself is untouched, still
reachable by typing its trigger phrase directly in supported apps and
configurable normally by anyone who wants it back; only the global
hotkey goes away.
Why this instead of moving the console's bind: the upcoming Quake
console (qconsole.lua, PR #7420) binds SUPER+grave:
o.bind("SUPER + grave", "Toggle scratchpad", hl.dsp.workspace.toggle_special("scratchpad"))
which is fcitx5's compiled-in default QuickPhrase trigger
(src/modules/quickphrase/quickphrase.h, fcitx/fcitx5):
KeyListOption triggerKey{
this, "TriggerKey", _("Trigger Key"),
{Key("Super+grave"), Key("Super+semicolon")},
...
Omarchy ships fcitx5 by default and currently overrides neither
trigger, so once this bind lands, QuickPhrase stops responding on
Super+grave with zero error and zero indication why: a Hyprland bind
with no non_consuming/auto_consuming flag consumes the key at the
compositor level, so the focused client, and therefore fcitx5, never
sees it. Confirmed not yet in a tagged release as of v4.0.4.
SUPER+grave is the right key for a Quake-style console; that shouldn't
have to move to accommodate an input-method addon almost nobody
configures. This is a one-line fix on the far less-visited side of the
collision.
View raw text
Recommendation: drop QuickPhrase's Super+grave trigger. It's a niche
feature most users never touch; the console is a deliberate, carefully
built one (multiple PRs on sizing, centering, agent-seeding). Add this
file, same pattern Omarchy already uses for clipboard.conf:
config/fcitx5/conf/quickphrase.conf
----------------------------------------
TriggerKey=
That's it. It's the identical override style already shipping today in
config/fcitx5/conf/clipboard.conf:
TriggerKey=
PastePrimaryKey=
which blanks a default fcitx5 trigger the same way. Copy the pattern,
new file, one line, done. QuickPhrase itself is untouched, still
reachable by typing its trigger phrase directly in supported apps and
configurable normally by anyone who wants it back; only the global
hotkey goes away.
Why this instead of moving the console's bind: the upcoming Quake
console (qconsole.lua, PR #7420) binds SUPER+grave:
o.bind("SUPER + grave", "Toggle scratchpad", hl.dsp.workspace.toggle_special("scratchpad"))
which is fcitx5's compiled-in default QuickPhrase trigger
(src/modules/quickphrase/quickphrase.h, fcitx/fcitx5):
KeyListOption triggerKey{
this, "TriggerKey", _("Trigger Key"),
{Key("Super+grave"), Key("Super+semicolon")},
...
Omarchy ships fcitx5 by default and currently overrides neither
trigger, so once this bind lands, QuickPhrase stops responding on
Super+grave with zero error and zero indication why: a Hyprland bind
with no non_consuming/auto_consuming flag consumes the key at the
compositor level, so the focused client, and therefore fcitx5, never
sees it. Confirmed not yet in a tagged release as of v4.0.4.
SUPER+grave is the right key for a Quake-style console; that shouldn't
have to move to accommodate an input-method addon almost nobody
configures. This is a one-line fix on the far less-visited side of the
collision.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.
- Out of scopeDecided by agents · verified · 2026-10-09 15:15 UTC