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.
First-agent OAuth browser opens tiled under the 875×600 setup terminal
Reported by unleashed-nick · filed Aug 16, 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
- Omarchy 4.0.0-1
- Hyprland 0.56.2
- ThinkPad T480, Intel Core i5-8350U, UHD Graphics 620
- Display: eDP-1 1920×1080 @ 1.6 scale (logical 1200×675)
- Chromium 151.0.7922.137-1
- Fresh install / first login
What's wrong?
On first-run, choosing a default agent (Grok) opens a floating org.omarchy.terminal installer (title "Omarchy"). After install it execs the agent in that same window. The agent then opens Chromium for device OAuth (https://accounts.x.ai/oauth2/device?...).
The login window appears centered under the installer. There is no obvious way to reach it.
Why
Shipped rules in default/hypr/apps/system.lua tag org.omarchy.terminal as floating-window: float, center, 875×600.
On a 1920×1080 panel at 1.6× scale the usable area is 1200×675, so that float covers almost the whole screen (≈160px sides, ≈37px top/bottom before bar and gaps).
default/hypr/apps/browser.lua forces Chromium tiled. Hyprland keeps floats above tiles, so the browser stays hidden. Alt+Tab can focus Chromium but cannot raise a tiled window above a float. Super+Tab only changes workspace.
Grok launches Chromium with a bare URL (uwsm-app -- /usr/bin/chromium 'https://accounts.x.ai/oauth2/device?...'), not omarchy-launch-browser, so the focus helper never runs. Even if it did, focus would not lift the tiled window above the float.
Journal for the session:
omarchy-default-agent --install grok
# via xdg-terminal-exec --app-id=org.omarchy.terminal --title=Omarchy
uwsm-app -- /usr/bin/chromium 'https://accounts.x.ai/oauth2/device?user_code=...'Steps to reproduce
- First login (or no default agent set).
- Use the "Set your default agent" invitation /
omarchy menu summon setup.default.agent. - Pick Grok (any agent that opens a browser to log in).
- Wait for the installer to start the agent and open the OAuth page.
Expected: the login page is visible and usable.
Actual: Chromium is tiled under the 875×600 centered float and cannot be reached.
Workaround
Super+drag the installer aside, or Super+T on it to tile both windows.
Notes
While the hidden Chromium window sat there it later aborted with SIGTRAP (GPU process isn't usable. Goodbye. from gpu_data_manager_impl_private.cc:417). That is a Chromium/Mesa abort, not this stacking bug.
Filed by Grok 4.6 via Grok Build.
View raw text
### System details - Omarchy 4.0.0-1 - Hyprland 0.56.2 - ThinkPad T480, Intel Core i5-8350U, UHD Graphics 620 - Display: eDP-1 1920×1080 @ 1.6 scale (logical 1200×675) - Chromium 151.0.7922.137-1 - Fresh install / first login ### What's wrong? On first-run, choosing a default agent (Grok) opens a floating `org.omarchy.terminal` installer (title "Omarchy"). After install it `exec`s the agent in that same window. The agent then opens Chromium for device OAuth (`https://accounts.x.ai/oauth2/device?...`). The login window appears **centered under** the installer. There is no obvious way to reach it. ### Why Shipped rules in `default/hypr/apps/system.lua` tag `org.omarchy.terminal` as `floating-window`: float, center, **875×600**. On a 1920×1080 panel at 1.6× scale the usable area is 1200×675, so that float covers almost the whole screen (≈160px sides, ≈37px top/bottom before bar and gaps). `default/hypr/apps/browser.lua` forces Chromium **tiled**. Hyprland keeps floats above tiles, so the browser stays hidden. `Alt+Tab` can focus Chromium but cannot raise a tiled window above a float. `Super+Tab` only changes workspace. Grok launches Chromium with a bare URL (`uwsm-app -- /usr/bin/chromium 'https://accounts.x.ai/oauth2/device?...'`), not `omarchy-launch-browser`, so the focus helper never runs. Even if it did, focus would not lift the tiled window above the float. Journal for the session: ``` omarchy-default-agent --install grok # via xdg-terminal-exec --app-id=org.omarchy.terminal --title=Omarchy uwsm-app -- /usr/bin/chromium 'https://accounts.x.ai/oauth2/device?user_code=...' ``` ### Steps to reproduce 1. First login (or no default agent set). 2. Use the "Set your default agent" invitation / `omarchy menu summon setup.default.agent`. 3. Pick Grok (any agent that opens a browser to log in). 4. Wait for the installer to start the agent and open the OAuth page. Expected: the login page is visible and usable. Actual: Chromium is tiled under the 875×600 centered float and cannot be reached. ### Workaround `Super`+drag the installer aside, or `Super+T` on it to tile both windows. ### Notes While the hidden Chromium window sat there it later aborted with SIGTRAP (`GPU process isn't usable. Goodbye.` from `gpu_data_manager_impl_private.cc:417`). That is a Chromium/Mesa abort, not this stacking bug. Filed by Grok 4.6 via Grok Build.
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 04:29 UTC