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-678GitHub issuePublicFixed

Default editor Zed not detected: menu/launcher check `zeditor` but Arch provides `zed`

Reported by onyvaxyz · filed Sep 11, 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; matches no known issue — decided by agents · verified. The outcome (valid, duplicate, not a bug, …) is not decided yet. See the decision.

Original report

Default editor Zed not detected: menu/launcher check `zeditor` but Arch provides `zed`revision 1 · captured 2026-09-28 21:23 UTC via poll

What happened

With Zed set as default editor (omarchy default editor → zeditor, XDG text/plain → dev.zed.Zed.desktop), the Omarchy menu under Setup → Defaults → Editor does not show Zed as checked / hides it, so Neovim looks like the standard editor. Additionally omarchy-launch-editor (EDITOR=omarchy-launch-editor --inline) falls back to nvim even though Zed is installed and configured.

Expected

Zed entry visible + checked in the menu, and omarchy-launch-editor launches Zed.

Steps to reproduce

  1. Install Zed via omarchy install editor-zed (installs Arch package providing /usr/bin/zed)
  2. omarchy default editor zed → writes zeditor to ~/.local/state/omarchy/defaults/editor
  3. omarchy-cmd-present zeditor; echo $? → 1 (missing), omarchy-cmd-present zed; echo $? → 0
  4. Menu entry setup.default.editor.zed has when: omarchy-cmd-present zeditor → hidden
  5. omarchy-launch-editor runs omarchy-cmd-present "$editor" || editor="nvim" → falls back to nvim

System

  • omarchy 4.0.3-1
  • zed-bin 1.19.2-1 owns /usr/bin/zed (wrapper around /usr/bin/zed.real), desktop file dev.zed.Zed.desktop with Exec=/usr/bin/zed %U
  • No zeditor binary on PATH

Affected files

  • default/omarchy/omarchy-menu.jsonc:163: "setup.default.editor.zed": {... "when":"omarchy-cmd-present zeditor" ...}
  • bin/omarchy-default-editor:21: zed | zeditor) editor="zeditor" ..
  • bin/omarchy-launch-editor:21: omarchy-cmd-present "$editor" || editor="nvim"

Note: omarchy-cmd-present requires ALL args present, so omarchy-cmd-present zed zeditor would not work as an OR-check.

Suggested fix

Accept both binary names, e.g. menu when: omarchy-cmd-present zed || omarchy-cmd-present zeditor, and resolve zeditor → zed in omarchy-launch-editor (or store zed as canonical name while still accepting zeditor for existing state files).

Local workaround

ln -s /usr/bin/zed ~/.local/bin/zeditor
omarchy menu refresh

This makes both the when guard and the launcher succeed again.

View raw text
## What happened

With Zed set as default editor (`omarchy default editor` → `zeditor`, XDG `text/plain` → `dev.zed.Zed.desktop`), the Omarchy menu under Setup → Defaults → Editor does not show Zed as checked / hides it, so Neovim looks like the standard editor. Additionally `omarchy-launch-editor` (`EDITOR=omarchy-launch-editor --inline`) falls back to `nvim` even though Zed is installed and configured.

## Expected

Zed entry visible + checked in the menu, and `omarchy-launch-editor` launches Zed.

## Steps to reproduce

1. Install Zed via `omarchy install editor-zed` (installs Arch package providing `/usr/bin/zed`)
2. `omarchy default editor zed` → writes `zeditor` to `~/.local/state/omarchy/defaults/editor`
3. `omarchy-cmd-present zeditor; echo $?` → 1 (missing), `omarchy-cmd-present zed; echo $?` → 0
4. Menu entry `setup.default.editor.zed` has `when: omarchy-cmd-present zeditor` → hidden
5. `omarchy-launch-editor` runs `omarchy-cmd-present "$editor" || editor="nvim"` → falls back to nvim

## System

- `omarchy 4.0.3-1`
- `zed-bin 1.19.2-1` owns `/usr/bin/zed` (wrapper around `/usr/bin/zed.real`), desktop file `dev.zed.Zed.desktop` with `Exec=/usr/bin/zed %U`
- No `zeditor` binary on PATH

## Affected files

- `default/omarchy/omarchy-menu.jsonc:163`: `"setup.default.editor.zed": {... "when":"omarchy-cmd-present zeditor" ...}`
- `bin/omarchy-default-editor:21`: `zed | zeditor) editor="zeditor" ..`
- `bin/omarchy-launch-editor:21`: `omarchy-cmd-present "$editor" || editor="nvim"`

Note: `omarchy-cmd-present` requires ALL args present, so `omarchy-cmd-present zed zeditor` would not work as an OR-check.

## Suggested fix

Accept both binary names, e.g. menu `when`: `omarchy-cmd-present zed || omarchy-cmd-present zeditor`, and resolve `zeditor` → `zed` in `omarchy-launch-editor` (or store `zed` as canonical name while still accepting `zeditor` for existing state files).

## Local workaround

```bash
ln -s /usr/bin/zed ~/.local/bin/zeditor
omarchy menu refresh
```
This makes both the `when` guard and the launcher succeed again.

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/11344· confirmed
  • Fixed bypr/13236· 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: matches no known issue

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