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.
ChatGPT/Codex floating voice overlay blocks clicks outside its visible controls
Reported by chaptersix · filed Oct 10, 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
What's wrong?
During an active voice conversation in the ChatGPT/Codex desktop app on Omarchy, moving away from the chat screen brings up a floating voice overlay in front of the application I am working in. Only a small chat bubble and a short activity/status blurb are visible, but a much larger section of the screen blocks mouse clicks to the application underneath.
The underlying application cannot be clicked in that area even where no overlay controls are visible.
Steps to reproduce
- Start a voice conversation in the ChatGPT/Codex desktop app on Omarchy.
- Move away from the chat screen to work in another application while voice remains active.
- With the floating voice overlay visible, try clicking the underlying application in the surrounding area outside the visible chat bubble and activity text.
Actual behavior
Clicks do not reach the application underneath across a larger area than the visible overlay content.
Expected behavior
The visible overlay controls should remain interactive, while transparent space outside those controls should allow clicks through to the underlying application.
Additional context
This is a floating overlay/input problem, rather than the overlay being allocated a full-sized tile. The companion pet may also be present, but the problem concerns the voice overlay and its surrounding click-blocking area.
This report describes user-observed behavior; the cause has not been diagnosed. It is unclear whether the input region is set by the app or handled incorrectly by the compositor. Exact Omarchy, Hyprland, and app versions, window metadata, and screenshots have not yet been collected.
View raw text
### What's wrong? During an active voice conversation in the ChatGPT/Codex desktop app on Omarchy, moving away from the chat screen brings up a floating voice overlay in front of the application I am working in. Only a small chat bubble and a short activity/status blurb are visible, but a much larger section of the screen blocks mouse clicks to the application underneath. The underlying application cannot be clicked in that area even where no overlay controls are visible. ### Steps to reproduce 1. Start a voice conversation in the ChatGPT/Codex desktop app on Omarchy. 2. Move away from the chat screen to work in another application while voice remains active. 3. With the floating voice overlay visible, try clicking the underlying application in the surrounding area outside the visible chat bubble and activity text. ### Actual behavior Clicks do not reach the application underneath across a larger area than the visible overlay content. ### Expected behavior The visible overlay controls should remain interactive, while transparent space outside those controls should allow clicks through to the underlying application. ### Additional context This is a floating overlay/input problem, rather than the overlay being allocated a full-sized tile. The companion pet may also be present, but the problem concerns the voice overlay and its surrounding click-blocking area. This report describes user-observed behavior; the cause has not been diagnosed. It is unclear whether the input region is set by the app or handled incorrectly by the compositor. Exact Omarchy, Hyprland, and app versions, window metadata, and screenshots have not yet been collected.
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-10 21:15 UTC