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.
playwright-cli bin clash
Reported by edradiark · filed Jul 16, 2026Closed upstream on 2026-07-18 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
System details
Intel i9-12900H, Intel Iris Xe (Alder Lake-P GT2), Omarchy 3.8.3
What's wrong?
install/packaging/npx.sh installs the core playwright package under the command name playwright-cli:
omarchy-npx-install playwright playwright-cli
That command name now belongs to a different, official package — @playwright/cli — whose own bin is also playwright-cli. Omarchy's shim in ~/.local/bin wins the PATH, so installing the official package appears to do nothing:
$ npm install -g @playwright/cli # installs 0.1.17
$ playwright-cli --version
Version 1.61.1 # <- core playwright, not @playwright/cli
It fails silently rather than loudly: both expose open, screenshot and pdf, so playwright-cli open runs core's opener, and only the later goto / click / snapshot calls error. Anything using the vendor's bundled agent skill (it hardcodes playwright-cli) misbehaves confusingly.
The name looks like a leftover rather than a deliberate choice. 948bac9f ("Fix install of playwright") changed:
-omarchy-npx-install playwright-cli
+omarchy-npx-install playwright playwright-cli
so the package originally targeted was one literally named playwright-cli. npm now deprecates that name:
This package is deprecated, use @playwright/cli instead.
@playwright/cli only became usable recently (0.1.17, published 2026-07-09), long after e294394b, so it wasn't an option at the time. It's the agent-facing CLI ("run playwright mcp commands from terminal"), which fits the intent of npx.sh — every other entry there is an AI coding agent.
Suggested fix, keeping core reachable under its real bin name so playwright test / codegen don't disappear:
-omarchy-npx-install playwright playwright-cli
+omarchy-npx-install @playwright/cli playwright-cli
+omarchy-npx-install playwright playwright
Repro: on a fresh Omarchy, npm install -g @playwright/cli, then playwright-cli --version → Version 1.61.1.
I could be wrong and there is another playwright-cli but this is the one I was trying to use when I got the clash.
View raw text
### System details
Intel i9-12900H, Intel Iris Xe (Alder Lake-P GT2), Omarchy 3.8.3
### What's wrong?
`install/packaging/npx.sh` installs the **core** `playwright` package under the command name `playwright-cli`:
omarchy-npx-install playwright playwright-cli
That command name now belongs to a different, official package — `@playwright/cli` — whose own bin is also `playwright-cli`. Omarchy's shim in `~/.local/bin` wins the PATH, so installing the official package appears to do nothing:
$ npm install -g @playwright/cli # installs 0.1.17
$ playwright-cli --version
Version 1.61.1 # <- core playwright, not @playwright/cli
It fails silently rather than loudly: both expose `open`, `screenshot` and `pdf`, so `playwright-cli open` runs core's opener, and only the later `goto` / `click` / `snapshot` calls error. Anything using the vendor's bundled agent skill (it hardcodes `playwright-cli`) misbehaves confusingly.
The name looks like a leftover rather than a deliberate choice. 948bac9f ("Fix install of playwright") changed:
-omarchy-npx-install playwright-cli
+omarchy-npx-install playwright playwright-cli
so the package originally targeted was one literally named `playwright-cli`. npm now deprecates that name:
> This package is deprecated, use @playwright/cli instead.
`@playwright/cli` only became usable recently (0.1.17, published 2026-07-09), long after e294394b, so it wasn't an option at the time. It's the agent-facing CLI ("run playwright mcp commands from terminal"), which fits the intent of npx.sh — every other entry there is an AI coding agent.
Suggested fix, keeping core reachable under its real bin name so `playwright test` / `codegen` don't disappear:
-omarchy-npx-install playwright playwright-cli
+omarchy-npx-install @playwright/cli playwright-cli
+omarchy-npx-install playwright playwright
Repro: on a fresh Omarchy, `npm install -g @playwright/cli`, then `playwright-cli --version` → `Version 1.61.1`.
I could be wrong and there is another playwright-cli but this is the one I was trying to use when I got the clash.
https://github.com/microsoft/playwright-cli
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.
No decision has been recorded yet.