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.
omarchy plugin update hides its confirm prompt behind git's pager when delta is not installed
Reported by elberacasa · filed Sep 17, 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, gum 2.0.0-1, delta not installed, default core.pager
What's wrong?
Without delta, omarchy plugin update <id> prints the diff with an unpiped git diff, so git opens its own pager. The gum confirm "Update <id>?" prompt then waits behind the pager, invisible. Enter scrolls one line inside less, so the update looks stuck with no sign that a keypress is expected. Quitting the pager with q reveals the prompt.
With delta installed the diff is piped, git disables its pager, and the prompt appears right away, so only installs without delta are affected.
bin/omarchy-plugin-update:
if omarchy-cmd-present delta; then
git -C "$dir" diff HEAD FETCH_HEAD | delta --paging=never
else
git -C "$dir" diff HEAD FETCH_HEAD # git pages this
fiSteps to reproduce
- Install a git-managed plugin and let it fall behind its upstream.
- Run
omarchy plugin update <id>in a terminal. - The diff fills the screen and nothing else happens; Enter scrolls one line at a time.
- Press
q: the confirm prompt appears.
Expected
The diff is shown without a pager, as on the delta path, so the confirm prompt is visible.
Suggested fix
One word, so both paths behave the same:
git -C "$dir" --no-pager diff HEAD FETCH_HEADbin/omarchy-plugin-add prints no diff, so this is the only place affected. Happy to send the patch as a pull request if that helps.
Workarounds
--yes, GIT_PAGER=cat omarchy plugin update <id>, or pressing q at the pager.
View raw text
### System details Omarchy 4.0.4-1, gum 2.0.0-1, delta not installed, default `core.pager` ### What's wrong? Without `delta`, `omarchy plugin update <id>` prints the diff with an unpiped `git diff`, so git opens its own pager. The `gum confirm "Update <id>?"` prompt then waits behind the pager, invisible. Enter scrolls one line inside `less`, so the update looks stuck with no sign that a keypress is expected. Quitting the pager with `q` reveals the prompt. With `delta` installed the diff is piped, git disables its pager, and the prompt appears right away, so only installs without `delta` are affected. `bin/omarchy-plugin-update`: ```sh if omarchy-cmd-present delta; then git -C "$dir" diff HEAD FETCH_HEAD | delta --paging=never else git -C "$dir" diff HEAD FETCH_HEAD # git pages this fi ``` ### Steps to reproduce 1. Install a git-managed plugin and let it fall behind its upstream. 2. Run `omarchy plugin update <id>` in a terminal. 3. The diff fills the screen and nothing else happens; Enter scrolls one line at a time. 4. Press `q`: the confirm prompt appears. ### Expected The diff is shown without a pager, as on the `delta` path, so the confirm prompt is visible. ### Suggested fix One word, so both paths behave the same: ```sh git -C "$dir" --no-pager diff HEAD FETCH_HEAD ``` `bin/omarchy-plugin-add` prints no diff, so this is the only place affected. Happy to send the patch as a pull request if that helps. ### Workarounds `--yes`, `GIT_PAGER=cat omarchy plugin update <id>`, or pressing `q` at the pager.
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
- Related PRpr/10248· confirmed
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 15:01 UTC