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.
Support non-interactive updates: omarchy update --yes flag
Reported by hummbl-dev · filed Aug 31, 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
Problem
omarchy update launches an interactive TUI confirmation prompt that cannot accept input from non-TTY shells. This blocks:
- SSH sessions without PTY allocation
- Automated/scheduled update pipelines
- AI agent-driven maintenance (e.g. devin CLI sessions)
Current workaround
sudo env OMARCHY_ALLOW_DIRECT_PACMAN=1 pacman -Syu --noconfirmThis bypasses the Omarchy wrapper entirely, skipping the update transcript, snapshot, keyrings, migrations, and post-update hooks that omarchy update handles.
Proposal
Add a --yes / -y flag to omarchy update that:
- Skips the interactive confirmation prompt
- Still runs the full Omarchy update pipeline (transcript, snapshot, hooks, restart checks)
- Prints a non-interactive summary to stdout instead of the TUI
omarchy update --yes # non-interactive, full pipelineContext
- Discovered during automated system maintenance on an Arch + Omarchy workstation
- The
OMARCHY_ALLOW_DIRECT_PACMAN=1escape hatch exists but is only surfaced in the pre-transaction hook error message, not in docs - AI agent runtimes (Devin CLI, Claude Code, etc.) cannot interact with TUI prompts
View raw text
## Problem `omarchy update` launches an interactive TUI confirmation prompt that cannot accept input from non-TTY shells. This blocks: - SSH sessions without PTY allocation - Automated/scheduled update pipelines - AI agent-driven maintenance (e.g. devin CLI sessions) ## Current workaround ```bash sudo env OMARCHY_ALLOW_DIRECT_PACMAN=1 pacman -Syu --noconfirm ``` This bypasses the Omarchy wrapper entirely, skipping the update transcript, snapshot, keyrings, migrations, and post-update hooks that `omarchy update` handles. ## Proposal Add a `--yes` / `-y` flag to `omarchy update` that: 1. Skips the interactive confirmation prompt 2. Still runs the full Omarchy update pipeline (transcript, snapshot, hooks, restart checks) 3. Prints a non-interactive summary to stdout instead of the TUI ```bash omarchy update --yes # non-interactive, full pipeline ``` ## Context - Discovered during automated system maintenance on an Arch + Omarchy workstation - The `OMARCHY_ALLOW_DIRECT_PACMAN=1` escape hatch exists but is only surfaced in the pre-transaction hook error message, not in docs - AI agent runtimes (Devin CLI, Claude Code, etc.) cannot interact with TUI prompts
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
- Fixed bypr/9511· 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 10:21 UTC