Proof Portal

Sign in
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-567GitHub issuePublicReceived

OpenClaw: stale omarchy-repo package shadows newer OpenClaw on PATH and breaks migrated state; Install menu re-offers it

Reported by aplaceforallmystuff · filed Sep 14, 2026Closed upstream on 2026-10-04 by the bot omarchybot; the closing comment says it was fixed by PR #13296. GitHub close reason: completed.

Open at source
Received and recorded verbatim. Nothing has been checked 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?
Not yet mapped to any requirement or component.
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. No decision has been recorded yet.

Original report

OpenClaw: stale omarchy-repo package shadows newer OpenClaw on PATH and breaks migrated state; Install menu re-offers itrevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

AMD Ryzen 5 Pro 7535U (Radeon iGPU), Omarchy 4.0.3-1, Arch Linux; OpenClaw 2026.9.3-1 (omarchy repo) alongside OpenClaw 2026.9.4 (npm, ~/.npm-global)

What's wrong?

When the openclaw package from the omarchy repo lags an OpenClaw release that migrates its state database, the packaged /usr/bin/openclaw shadows the newer install and silently breaks OpenClaw, and the Install menu later re-offers the stale package.

What happened

  1. The omarchy repo shipped openclaw 2026.9.3. OpenClaw 2026.9.4 was installed via npm (to get the newer release), and its Gateway migrated ~/.openclaw/state/openclaw.sqlite to schema 17.
  2. /usr/bin precedes user bin dirs on PATH, so plain openclaw kept resolving to the packaged 2026.9.3 build, which refuses the migrated data:
   OpenClaw state database ~/.openclaw/state/openclaw.sqlite uses newer schema version 17; this build supports 16.
   Refused by OpenClaw 2026.9.3 (1391f7c) installed at /usr/lib/node_modules/openclaw.
  1. Everything that invokes bare openclaw failed without much visibility: OpenClaw's own scheduled backup job (openclaw backup git create) failed daily for 6 days, and openclaw update repair looped. The Gateway systemd unit generated for the package also kept ExecStart pointing at /usr/lib/node_modules/openclaw.
  2. After removing the package (pacman -R openclaw), Menu › Install › AI › OpenClaw reappears because its gate is ! omarchy-pkg-present openclaw, even though a working OpenClaw install and running Gateway exist. Selecting it runs omarchy-pkg-add openclaw → pacman -S --noconfirm --needed openclaw, which reinstalls the stale binary ahead of the working one on PATH (and --noconfirm also answers yes to an IgnorePkg prompt).

Steps to reproduce

  1. Install OpenClaw from the Omarchy menu (package 2026.9.3).
  2. Install a newer OpenClaw that bumps the DB schema (e.g. npm i -g [email protected]) and start its Gateway so it migrates state.
  3. Run openclaw status → the packaged build refuses the data.
  4. sudo pacman -R openclaw, open Menu › Install › AI → OpenClaw is offered again and would reinstate the stale binary.

Possible fixes

  • Keep the openclaw package in lockstep with OpenClaw releases that change the state schema.
  • Gate the install menu entry on an existing OpenClaw (command -v openclaw or an installed openclaw-gateway.service), not only the pacman package.
  • Optionally warn in omarchy-launch-openclaw when more than one openclaw is on PATH.

Related packaging issue: #11753

View raw text
### System details

AMD Ryzen 5 Pro 7535U (Radeon iGPU), Omarchy 4.0.3-1, Arch Linux; OpenClaw 2026.9.3-1 (omarchy repo) alongside OpenClaw 2026.9.4 (npm, `~/.npm-global`)

### What's wrong?

When the `openclaw` package from the omarchy repo lags an OpenClaw release that migrates its state database, the packaged `/usr/bin/openclaw` shadows the newer install and silently breaks OpenClaw, and the Install menu later re-offers the stale package.

**What happened**

1. The omarchy repo shipped `openclaw` 2026.9.3. OpenClaw 2026.9.4 was installed via npm (to get the newer release), and its Gateway migrated `~/.openclaw/state/openclaw.sqlite` to schema 17.
2. `/usr/bin` precedes user bin dirs on `PATH`, so plain `openclaw` kept resolving to the packaged 2026.9.3 build, which refuses the migrated data:
   ```
   OpenClaw state database ~/.openclaw/state/openclaw.sqlite uses newer schema version 17; this build supports 16.
   Refused by OpenClaw 2026.9.3 (1391f7c) installed at /usr/lib/node_modules/openclaw.
   ```
3. Everything that invokes bare `openclaw` failed without much visibility: OpenClaw's own scheduled backup job (`openclaw backup git create`) failed daily for 6 days, and `openclaw update repair` looped. The Gateway systemd unit generated for the package also kept `ExecStart` pointing at `/usr/lib/node_modules/openclaw`.
4. After removing the package (`pacman -R openclaw`), **Menu › Install › AI › OpenClaw** reappears because its gate is `! omarchy-pkg-present openclaw`, even though a working OpenClaw install and running Gateway exist. Selecting it runs `omarchy-pkg-add openclaw` → `pacman -S --noconfirm --needed openclaw`, which reinstalls the stale binary ahead of the working one on `PATH` (and `--noconfirm` also answers yes to an `IgnorePkg` prompt).

**Steps to reproduce**

1. Install OpenClaw from the Omarchy menu (package 2026.9.3).
2. Install a newer OpenClaw that bumps the DB schema (e.g. `npm i -g [email protected]`) and start its Gateway so it migrates state.
3. Run `openclaw status` → the packaged build refuses the data.
4. `sudo pacman -R openclaw`, open Menu › Install › AI → OpenClaw is offered again and would reinstate the stale binary.

**Possible fixes**

- Keep the `openclaw` package in lockstep with OpenClaw releases that change the state schema.
- Gate the install menu entry on an existing OpenClaw (`command -v openclaw` or an installed `openclaw-gateway.service`), not only the pacman package.
- Optionally warn in `omarchy-launch-openclaw` when more than one `openclaw` is on `PATH`.

Related packaging issue: #11753

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

No decision has been recorded yet.