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.
Install > Web App displays Done after validation failure
Reported by scossar · filed Sep 4, 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
MSI Stealth 15M A11UEK, Intel Core i7-11375H, Intel Iris Xe + NVIDIA RTX 3060 Laptop GPU, Omarchy 4.0.2-1, Hyprland 0.56.2
What's wrong?
Install > Web App displays the green Done! prompt after the installer rejects invalid input and exits with an error.
This was reproduced twice:
- Open the Omarchy menu.
- Select
Install > Web App. - At the
Name>prompt, enterhttp://localhost:1234.
The terminal displays:
Let's create a new web app you can start with the app launcher.
App name cannot contain '/': http://localhost:1234
● Done! Press any key to close...The validation error is correct: the URL was entered where an app name was requested. The subsequent success message is not.
Expected
When the invoked command exits unsuccessfully, the presentation terminal should preserve/display the failure without showing Done!. Ideally the terminal would remain available long enough to read the error or retry, but the essential issue is that failure must not be reported as success.
Actual
The installer exits with status 1, then the presentation wrapper displays the same Done! prompt used after successful completion.
Cause
omarchy-webapp-install calls require_plain_name, which prints the validation error and exits 1. omarchy-launch-floating-terminal-with-presentation then runs:
omarchy-show-logo; $cmd; if (( $? != 130 )); then omarchy-show-done; fiThis suppresses Done! only for status 130. Every other nonzero exit status is presented as successful completion. This likely affects other commands launched through the same presentation wrapper. Related issue #9526 observes the same wrapper behavior in a different failure path.
Optional UX follow-up
A URL entered as the first response could be recognized and handled more helpfully: either explain that an app name is required and reprompt, or support a URL-first flow that fetches the page title for the app name in the same general way the installer already attempts to fetch the site icon. This enhancement is not required to resolve the misleading-success bug.
View raw text
### System details MSI Stealth 15M A11UEK, Intel Core i7-11375H, Intel Iris Xe + NVIDIA RTX 3060 Laptop GPU, Omarchy 4.0.2-1, Hyprland 0.56.2 ### What's wrong? `Install > Web App` displays the green **Done!** prompt after the installer rejects invalid input and exits with an error. This was reproduced twice: 1. Open the Omarchy menu. 2. Select `Install > Web App`. 3. At the `Name>` prompt, enter `http://localhost:1234`. The terminal displays: ```text Let's create a new web app you can start with the app launcher. App name cannot contain '/': http://localhost:1234 ● Done! Press any key to close... ``` The validation error is correct: the URL was entered where an app name was requested. The subsequent success message is not. #### Expected When the invoked command exits unsuccessfully, the presentation terminal should preserve/display the failure without showing **Done!**. Ideally the terminal would remain available long enough to read the error or retry, but the essential issue is that failure must not be reported as success. #### Actual The installer exits with status 1, then the presentation wrapper displays the same **Done!** prompt used after successful completion. #### Cause `omarchy-webapp-install` calls `require_plain_name`, which prints the validation error and exits 1. `omarchy-launch-floating-terminal-with-presentation` then runs: ```bash omarchy-show-logo; $cmd; if (( $? != 130 )); then omarchy-show-done; fi ``` This suppresses **Done!** only for status 130. Every other nonzero exit status is presented as successful completion. This likely affects other commands launched through the same presentation wrapper. Related issue #9526 observes the same wrapper behavior in a different failure path. #### Optional UX follow-up A URL entered as the first response could be recognized and handled more helpfully: either explain that an app name is required and reprompt, or support a URL-first flow that fetches the page title for the app name in the same general way the installer already attempts to fetch the site icon. This enhancement is not required to resolve the misleading-success bug.
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 10:44 UTC