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.
Voice-to-text loses the intended text-field focus
Reported by jordatech · filed Oct 2, 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
System details
HP OMEN MAX Gaming Laptop 16 omarchy 4.0.4-1 NVIDIA RTX 5080 Intel Core Ultra 9 275HX
What's wrong?
- Voice-to-text loses the intended text-field focus
Problem:
When using Omarchy's voice-to-text shortcut (Ctrl + Super + X) with multiple monitors, dictation does not remain reliably attached to the text field that was selected when dictation started.
Example:
Click into a text box.
Start voice-to-text with Ctrl + Super + X.
Move the mouse to another window, application, or monitor without clicking.
Dictated text may begin appearing wherever the mouse is hovering instead of continuing in the original text field.
This is especially problematic because moving the mouse alone should not change the destination of dictated text.
Desired behavior:
When voice-to-text starts, lock the output destination to the currently focused text field.
Mouse movement alone should never redirect dictation.
Keep sending text to that field until dictation ends or the user explicitly changes focus by clicking/selecting another field.
Ideally also maintain the complete transcription in a clipboard/buffer so the entire dictation can be pasted again if text is accidentally sent to the wrong place.
View raw text
### System details HP OMEN MAX Gaming Laptop 16 omarchy 4.0.4-1 NVIDIA RTX 5080 Intel Core Ultra 9 275HX ### What's wrong? 1. Voice-to-text loses the intended text-field focus Problem: When using Omarchy's voice-to-text shortcut (Ctrl + Super + X) with multiple monitors, dictation does not remain reliably attached to the text field that was selected when dictation started. Example: Click into a text box. Start voice-to-text with Ctrl + Super + X. Move the mouse to another window, application, or monitor without clicking. Dictated text may begin appearing wherever the mouse is hovering instead of continuing in the original text field. This is especially problematic because moving the mouse alone should not change the destination of dictated text. Desired behavior: When voice-to-text starts, lock the output destination to the currently focused text field. Mouse movement alone should never redirect dictation. Keep sending text to that field until dictation ends or the user explicitly changes focus by clicking/selecting another field. Ideally also maintain the complete transcription in a clipboard/buffer so the entire dictation can be pasted again if text is accidentally sent to the wrong place. [omarchy-issue-details-20261002-164314.txt](https://github.com/user-attachments/files/32956763/omarchy-issue-details-20261002-164314.txt) [about.txt](https://github.com/user-attachments/files/32956741/about.txt)
- omarchy-issue-details-20261002-164314.txt
- about.txt
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 20:40 UTC