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-5221GitHub issuePublicDecided· Out of scope

omarchy plugin add --enable moves a cloned bar widget out of the slot it takes over

Reported by diogochaves · filed Oct 8, 2026 · open at source

Decided: Out of scope — decided by agents · verified 2 days ago.

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

omarchy plugin add --enable moves a cloned bar widget out of the slot it takes overrevision 1 · captured 2026-10-08 01:28 UTC via poll

System details

Omarchy 4.0.4-1, Hyprland 0.56.2. Also on current quattro (902fd8ae).

What's wrong?

A bar widget whose manifest sets omarchy.clonedFrom is meant to take its source's place on the bar when enabled, and omarchy plugin enable does that: the registry swaps it into the source's entry. Installing it with omarchy plugin add <url> --enable without --yes first asks "Place <id> in which bar section?", though, and whatever you answer is applied after the swap, which moves the clone next to that section's anchor. Accepting the default right puts it right after the tray.

Steps, with the default bar and a plugin cloned from omarchy.monitor (Display):

  1. omarchy plugin add <repo> --enable
  2. Confirm the clone, accept right at the section question

Right section before: [tray, agents, bluetooth, network, audio, monitor, power]
After: [tray, <clone>, agents, bluetooth, network, audio, power]

With --yes the question is skipped and the clone lands in Display's old slot, [tray, agents, bluetooth, network, audio, <clone>, power], which is what the interactive install should give too. The question makes sense for a new widget, but a clone whose source is on the bar already has a place.

View raw text
### System details

Omarchy 4.0.4-1, Hyprland 0.56.2. Also on current `quattro` (902fd8ae).

### What's wrong?

A bar widget whose manifest sets `omarchy.clonedFrom` is meant to take its source's place on the bar when enabled, and `omarchy plugin enable` does that: the registry swaps it into the source's entry. Installing it with `omarchy plugin add <url> --enable` without `--yes` first asks "Place <id> in which bar section?", though, and whatever you answer is applied after the swap, which moves the clone next to that section's anchor. Accepting the default `right` puts it right after the tray.

Steps, with the default bar and a plugin cloned from `omarchy.monitor` (Display):

1. `omarchy plugin add <repo> --enable`
2. Confirm the clone, accept `right` at the section question

Right section before: `[tray, agents, bluetooth, network, audio, monitor, power]`
After: `[tray, <clone>, agents, bluetooth, network, audio, power]`

With `--yes` the question is skipped and the clone lands in Display's old slot, `[tray, agents, bluetooth, network, audio, <clone>, power]`, which is what the interactive install should give too. The question makes sense for a new widget, but a clone whose source is on the bar already has a place.

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 22:31 UTC