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.
Install Gemini CLI fails: mise __node-gyp-bootstrap errors with "no tasks defined"
Reported by kevincardwell · filed Aug 26, 2026 · open at source
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
What happened
Clicking "Install Gemini" in the Omarchy menu fails. The installer output shows:
mise ERROR no tasks defined in ~/.local/share/mise/installs/gemini/0.56.0/node_modules/.mise/[email protected]/node_modules/node-pty. Are you in a project directory?
mise ERROR Failed to install npm:@google/gemini-cli@latest: aube install failed: lifecycle script install failed for [email protected]: script `install` exited with code Some(1)
Could not install Gemini with miseExpected: Gemini CLI installs successfully.
Steps to reproduce
mise install -f gemini(equivalent to clicking "Install Gemini" in the menu, which runs the ~/.local/bin/gemini wrapper generated by omarchy-mise-install gemini)
Root cause (confirmed via `MISE_VERBOSE=1`)
Omarchy's own script is not at fault — omarchy-mise-install just does mise use -g gemini. The failure happens inside mise itself: mise's aube npm backend tries to build the native [email protected] dependency (pulled in transitively via @github/keytar) by shelling out to mise __node-gyp-bootstrap <dir>, which then fails because it runs mise's task-runner against the node-pty package dir, which has no mise tasks defined. This reproduces with plain npm install [email protected] working fine outside of mise, so it looks like a bug in mise's own __node-gyp-bootstrap command, not a system toolchain issue (build tools, Python, etc. are all present and working).
System details
- Omarchy: 4.0.1-1
- mise: 2026.8.11 linux-x64 (a newer 2026.8.14 is available, unconfirmed whether it fixes this)
- Kernel: 7.1.9-arch1-2, Hyprland 0.56.2
- CPU: AMD Ryzen 9 5950X / GPU: NVIDIA RTX 4070 Ti
<img width="1921" height="1129" alt="Image" src="https://github.com/user-attachments/assets/8f89c1bc-c72f-40e8-81c9-0a7a5eeada6b" />
View raw text
**What happened** Clicking "Install Gemini" in the Omarchy menu fails. The installer output shows: ``` mise ERROR no tasks defined in ~/.local/share/mise/installs/gemini/0.56.0/node_modules/.mise/[email protected]/node_modules/node-pty. Are you in a project directory? mise ERROR Failed to install npm:@google/gemini-cli@latest: aube install failed: lifecycle script install failed for [email protected]: script `install` exited with code Some(1) Could not install Gemini with mise ``` **Expected:** Gemini CLI installs successfully. **Steps to reproduce** ``` mise install -f gemini ``` (equivalent to clicking "Install Gemini" in the menu, which runs the `~/.local/bin/gemini` wrapper generated by `omarchy-mise-install gemini`) **Root cause (confirmed via `MISE_VERBOSE=1`)** Omarchy's own script is not at fault — `omarchy-mise-install` just does `mise use -g gemini`. The failure happens inside mise itself: mise's `aube` npm backend tries to build the native `[email protected]` dependency (pulled in transitively via `@github/keytar`) by shelling out to `mise __node-gyp-bootstrap <dir>`, which then fails because it runs mise's task-runner against the `node-pty` package dir, which has no mise tasks defined. This reproduces with plain `npm install [email protected]` working fine outside of mise, so it looks like a bug in mise's own `__node-gyp-bootstrap` command, not a system toolchain issue (build tools, Python, etc. are all present and working). **System details** - Omarchy: 4.0.1-1 - mise: 2026.8.11 linux-x64 (a newer 2026.8.14 is available, unconfirmed whether it fixes this) - Kernel: 7.1.9-arch1-2, Hyprland 0.56.2 - CPU: AMD Ryzen 9 5950X / GPU: NVIDIA RTX 4070 Ti <img width="1921" height="1129" alt="Image" src="https://github.com/user-attachments/assets/8f89c1bc-c72f-40e8-81c9-0a7a5eeada6b" />
- 8f89c1bc-c72f-40e8-81c9-0a7a5eeada6b
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 09:12 UTC