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.
Launching things into floating windows or empty workspaces
Reported by chadbailey59 · filed Sep 18, 2025Closed upstream on 2026-02-01 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
What do you need?
Somewhat inspired by omarchy-launch-or-focus, I want to be able to do two things:
- Launch an app immediately into a floating window instead of a tiled window.
- Launch an app into the first empty hyprland workspace (on my current monitor using hyprland split-monitor-workspaces, but that's not important for now).
I have this working for things I launch with Hyprland:
# SUPER-T gives me a quick floating terminal
bind = SUPER SHIFT, T, exec, $TERMINAL --class floating-terminal
windowrulev2 = float, class:floating-terminal
windowrulev2 = size 800 600, class:floating-terminal
windowrulev2 = center, class:floating-terminal
# SUPER-ALT-T opens a terminal in the first empty workspace
bind = SUPER ALT, T, exec, [workspace empty] $TERMINALI want to be able to do this with Walker as well. In my head, I'd type a few letters to find a less commonly-used app, then shift-enter to make it float, or alt-enter to launch it in an empty workspace. When I brought it up in the Walker discord, I got conflicting reports of whether it would be 1) possible, or 2) accepted as a PR.
So in the DHH spirit of "you can just do things", I might still try it anyway... but does anyone else have ideas about how this could be implemented? It feels like one of these omarchy wrappers might be involved.
View raw text
### What do you need? Somewhat inspired by `omarchy-launch-or-focus`, I want to be able to do two things: 1. Launch an app immediately into a floating window instead of a tiled window. 2. Launch an app into the first empty hyprland workspace (on my current monitor using hyprland split-monitor-workspaces, but that's not important for now). I have this working for things I launch with Hyprland: ``` # SUPER-T gives me a quick floating terminal bind = SUPER SHIFT, T, exec, $TERMINAL --class floating-terminal windowrulev2 = float, class:floating-terminal windowrulev2 = size 800 600, class:floating-terminal windowrulev2 = center, class:floating-terminal # SUPER-ALT-T opens a terminal in the first empty workspace bind = SUPER ALT, T, exec, [workspace empty] $TERMINAL ``` I want to be able to do this with Walker as well. In my head, I'd type a few letters to find a less commonly-used app, then shift-enter to make it float, or alt-enter to launch it in an empty workspace. When I brought it up in the Walker discord, I got conflicting reports of whether it would be 1) possible, or 2) accepted as a PR. So in the DHH spirit of "you can just do things", I might still try it anyway... but does anyone else have ideas about how this could be implemented? It feels like one of these `omarchy` wrappers might be involved.
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.
No decision has been recorded yet.