Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-604GitHub issuePublicReceived

Documentation corrections: missing commands (windows key, ascii), clipboard controls, and wifi-qr condition

Reported by mmr2070 · filed Sep 13, 2026 · open at source

Partly in the audited area (menu) — decided by agents · verified. Not validated yet.

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?
AreaPartly in the audited areamenu· 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?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. So far: partly in the audited area (menu) — decided by agents · verified; intended behaviour — a design question, not a defect — decided by agents · verified; not a duplicate of another report — decided by agents · verified. The outcome (valid, duplicate, not a bug, …) is not decided yet. See the decision.

Original report

Documentation corrections: missing commands (windows key, ascii), clipboard controls, and wifi-qr conditionrevision 1 · captured 2026-09-28 21:23 UTC via poll

Issue A: omarchy windows key Does Not Exist

  • Manual Reference: Section on Windows VM:
"If this computer shipped with Windows, the OEM key is still in firmware even after installing Omarchy. Print it with `omarchy windows key`."
  • Actual Behavior: The command fails with:
  $ omarchy windows key
  Unknown Omarchy command: omarchy windows key

Only omarchy windows vm <install|remove|launch|stop|status> is packaged in /usr/share/omarchy/bin/.
- Underlying Workaround for Users:

  sudo strings /sys/firmware/acpi/tables/MSDM
  • Report Recommendation: File an issue or docs PR asking whether omarchy-windows-key was intended to be added to bin/ (reading /sys/firmware/acpi/tables/MSDM), or if the manual needs to be updated.

Issue B: omarchy ascii Does Not Exist

  • Manual Reference: Section on Branding / Screensaver:
"`omarchy ascii` draws text in Delta Corps Priest 1... `omarchy ascii \"Back in five\" > ~/.config/omarchy/branding/screensaver.txt`"
  • Actual Behavior:
  $ omarchy ascii "Back in five"
  Unknown Omarchy command: omarchy ascii

The branding commands in the binary are:
- omarchy branding screensaver text (opens ~/.config/omarchy/branding/screensaver.txt in the default editor)
- omarchy branding screensaver image (converts an image using omarchy transcode ascii)
- omarchy branding screensaver reset (resets to default logo)
- Report Recommendation: Update the documentation to reflect omarchy branding screensaver text or package the missing omarchy-ascii FIGlet wrapper.


Issue C: Undocumented Wi-Fi Dependency for Setup > Network > QR Code

  • Manual Reference: Section on Network Sharing:
"Rather than reading a long password out loud, run Setup > Network > QR Code while you’re on Wi-Fi."
  • Problem: When a computer is connected via wired Ethernet (e.g. eno1) or Wi-Fi is not the active default route, the option completely disappears from the menu without explanation.
  • Cause: In /usr/share/omarchy/default/omarchy/omarchy-menu.jsonc:
  "when": "[[ $(omarchy-network-status) == wifi* ]]"
  • Report Recommendation: Either document that this menu entry requires Wi-Fi to be the primary active connection, or have the menu item present a friendly disabled message when clicked (e.g. "Wi-Fi is not connected").

Issue D: Missing Documentation for Clipboard Manager Controls

  • Manual Reference: The manual mentions Super + Ctrl + V to toggle the clipboard, but lacks instructions on how to manage or delete items.
  • Hidden Features in UI:
  • Delete: Deletes the highlighted clipboard entry.
  • Shift + Delete: Opens a confirmation dialog to wipe all clipboard history.
  • Terminal clear: echo "[]" > ~/.local/state/omarchy/clipboard-history.json
  • Report Recommendation: Add a table or note to the manual detailing the Delete and Shift + Delete key actions.
View raw text
### Issue A: `omarchy windows key` Does Not Exist
- **Manual Reference**: Section on Windows VM:
  > *"If this computer shipped with Windows, the OEM key is still in firmware even after installing Omarchy. Print it with `omarchy windows key`."*
- **Actual Behavior**: The command fails with:
  ```bash
  $ omarchy windows key
  Unknown Omarchy command: omarchy windows key
  ```
  Only `omarchy windows vm <install|remove|launch|stop|status>` is packaged in `/usr/share/omarchy/bin/`.
- **Underlying Workaround for Users**: 
  ```bash
  sudo strings /sys/firmware/acpi/tables/MSDM
  ```
- **Report Recommendation**: File an issue or docs PR asking whether `omarchy-windows-key` was intended to be added to `bin/` (reading `/sys/firmware/acpi/tables/MSDM`), or if the manual needs to be updated.

---

### Issue B: `omarchy ascii` Does Not Exist
- **Manual Reference**: Section on Branding / Screensaver:
  > *"`omarchy ascii` draws text in Delta Corps Priest 1... `omarchy ascii \"Back in five\" > ~/.config/omarchy/branding/screensaver.txt`"*
- **Actual Behavior**:
  ```bash
  $ omarchy ascii "Back in five"
  Unknown Omarchy command: omarchy ascii
  ```
  The branding commands in the binary are:
  - `omarchy branding screensaver text` (opens `~/.config/omarchy/branding/screensaver.txt` in the default editor)
  - `omarchy branding screensaver image` (converts an image using `omarchy transcode ascii`)
  - `omarchy branding screensaver reset` (resets to default logo)
- **Report Recommendation**: Update the documentation to reflect `omarchy branding screensaver text` or package the missing `omarchy-ascii` FIGlet wrapper.

---

### Issue C: Undocumented Wi-Fi Dependency for *Setup > Network > QR Code*
- **Manual Reference**: Section on Network Sharing:
  > *"Rather than reading a long password out loud, run Setup > Network > QR Code while you’re on Wi-Fi."*
- **Problem**: When a computer is connected via wired Ethernet (e.g. `eno1`) or Wi-Fi is not the active default route, the option completely disappears from the menu without explanation.
- **Cause**: In `/usr/share/omarchy/default/omarchy/omarchy-menu.jsonc`:
  ```json
  "when": "[[ $(omarchy-network-status) == wifi* ]]"
  ```
- **Report Recommendation**: Either document that this menu entry requires Wi-Fi to be the primary active connection, or have the menu item present a friendly disabled message when clicked (e.g. *"Wi-Fi is not connected"*).

---

### Issue D: Missing Documentation for Clipboard Manager Controls
- **Manual Reference**: The manual mentions `Super + Ctrl + V` to toggle the clipboard, but lacks instructions on how to manage or delete items.
- **Hidden Features in UI**:
  - `Delete`: Deletes the highlighted clipboard entry.
  - `Shift + Delete`: Opens a confirmation dialog to wipe all clipboard history.
  - Terminal clear: `echo "[]" > ~/.local/state/omarchy/clipboard-history.json`
- **Report Recommendation**: Add a table or note to the manual detailing the `Delete` and `Shift + Delete` key actions.

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/11677· 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.

  • Decided by agents · verified: partly in the audited area (menu)
  • Decided by agents · verified: intended behaviour — a design question, not a defect
  • Decided by agents · verified: not a duplicate of another report

The outcome (valid, duplicate, not a bug, …) is not decided yet.