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.
Agent setup's floating terminal covers the browser during provider login
Reported by rlpeacock · filed Oct 5, 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.4-1
- Hyprland: 0.56.2
- Kernel: 7.2.5-3-omarchy
- CPU: Intel Core i7-9700
- GPU: Intel UHD Graphics 630 (CoffeeLake-S GT2)
Description
When you set up a coding agent from the "set up AI assistant" prompt notification, the install runs in a floating terminal. After the install, the agent starts inside that same floating window. When the agent's first-run login (e.g. Claude) opens the provider's auth page, the browser opens underneath the floating terminal and can't be brought in front of it. You can't finish authentication without knowing to tile the terminal manually (SUPER + T).
Steps to reproduce
- On a system with no default agent installed, select the "set up AI assistant" notification.
- Pick Claude (or another agent that logs in through a browser).
- Wait for the install to finish and the agent to start in the same terminal.
- Choose to log in with the provider.
Expected: The auth page is visible and usable.
Actual: The browser opens as a tiled window behind the centered floating terminal and stays covered.
Cause
omarchy-default-agentruns the install via
omarchy-launch-floating-terminal-with-presentation, which uses app-id
org.omarchy.terminal. default/hypr/apps/system.lua tags that app-id
floating-window (float, center, 875×600).
- After installing, it runs exec omarchy-agent --inline, so the agent and
its browser-based login run in that floating window.
- default/hypr/apps/browser.lua forces Chromium-based browsers to tile = true.
Hyprland always draws floating windows above tiled ones, so the browser
can't come to the front.
Possible fixes
- Hand off to a normal tiled agent window after the install (e.g.
exec omarchy-agent
instead of --inline, so the window gets the org.omarchy.agent app-id) rather than
continuing in the floating presentation terminal.
- Or launch the install terminal with a different app-id that isn't tagged floating-window.
Workaround
Focus the setup terminal and press SUPER + T to tile it, then finish the login in the browser.
View raw text
### System details - Omarchy: 4.0.4-1 - Hyprland: 0.56.2 - Kernel: 7.2.5-3-omarchy - CPU: Intel Core i7-9700 - GPU: Intel UHD Graphics 630 (CoffeeLake-S GT2) ### Description When you set up a coding agent from the "set up AI assistant" prompt notification, the install runs in a floating terminal. After the install, the agent starts inside that same floating window. When the agent's first-run login (e.g. Claude) opens the provider's auth page, the browser opens **underneath** the floating terminal and can't be brought in front of it. You can't finish authentication without knowing to tile the terminal manually (SUPER + T). ### Steps to reproduce 1. On a system with no default agent installed, select the "set up AI assistant" notification. 2. Pick Claude (or another agent that logs in through a browser). 3. Wait for the install to finish and the agent to start in the same terminal. 4. Choose to log in with the provider. **Expected:** The auth page is visible and usable. **Actual:** The browser opens as a tiled window behind the centered floating terminal and stays covered. ### Cause - `omarchy-default-agent` runs the install via `omarchy-launch-floating-terminal-with-presentation`, which uses app-id `org.omarchy.terminal`. `default/hypr/apps/system.lua` tags that app-id `floating-window` (float, center, 875×600). - After installing, it runs `exec omarchy-agent --inline`, so the agent and its browser-based login run in that floating window. - `default/hypr/apps/browser.lua` forces Chromium-based browsers to `tile = true`. Hyprland always draws floating windows above tiled ones, so the browser can't come to the front. ### Possible fixes - Hand off to a normal tiled agent window after the install (e.g. `exec omarchy-agent` instead of `--inline`, so the window gets the `org.omarchy.agent` app-id) rather than continuing in the floating presentation terminal. - Or launch the install terminal with a different app-id that isn't tagged `floating-window`. ### Workaround Focus the setup terminal and press SUPER + T to tile it, then finish the login in the browser.
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 21:26 UTC