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.
omarchy-mise-install wrappers infinite-loop when mise's PATH hook isn't active (related #3685)
Reported by husamemadH · filed Jul 23, 2026Closed upstream on 2026-07-24 by its own reporter husamemadH. GitHub close reason: completed. Closed by its own reporter — not by itself 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
mise ~/.config/mise/config.toml tools: [email protected]
System details
Intel Core i7-8665U · Intel UHD Graphics 620 · Omarchy 4.0.0.alpha · mise 2026.7.10
What's wrong?
Every tool wrapper generated by bin/omarchy-mise-install (claude, codex, gemini, copilot, opencode, gh, pi, ghui, hunk, playwright…) can enter an infinite loop that repeatedly prints the mise use line and never launches the tool.
Root cause. The generated wrapper (~/.local/bin/$command) is:
#!/bin/bash
mise use -g "$package"
exec "$bin" "$@"exec "$bin" resolves $bin by name through PATH. When $command == $bin (e.g. claude→claude) and ~/.local/bin sits before mise's installs/<tool>/latest in PATH, exec "$bin" re-finds the wrapper itself → runs mise use -g again → execs itself again → infinite loop. Each iteration prints the mise line, which is the visible symptom.
Why it hits stock installs. mise keeps installs/<tool>/latest ahead of ~/.local/bin via _mise_hook in PROMPT_COMMAND. Per #3685, starship/zoxide (omarchy defaults) overwrite PROMPT_COMMAND and drop _mise_hook, so the prepend stops. Ordinary tools then fall back to system versions (#3685's complaint), but these wrappers infinite-loop instead. Also reachable transiently at fresh-shell startup before the first prompt hook fires.
Steps to reproduce.
# state where mise hasn't prepended the install dir
PATH="$HOME/.local/bin:$HOME/.local/share/mise/shims:/usr/bin:/bin" claudeIt spins forever, printing this line on every iteration and never launching the tool:
mise ~/.config/mise/config.toml tools: [email protected]
mise ~/.config/mise/config.toml tools: [email protected]
mise ~/.config/mise/config.toml tools: [email protected]
... (~28 iterations in 3s before `timeout` kills it with exit code 124)Workaround: run any mise command first so the hook re-prepends the install dir.
Suggested fix (keeps lazy install; correct regardless of PATH ordering; scoped to the one package so it doesn't leak other runtimes (node/java/etc.) into the tool's PATH):
mise use -g "$package"
exec mise exec "$package" -- "$bin" "$@"Verified against all affected wrappers. PR incoming.
View raw text
mise ~/.config/mise/config.toml tools: [email protected] ### System details Intel Core i7-8665U · Intel UHD Graphics 620 · Omarchy 4.0.0.alpha · mise 2026.7.10 ### What's wrong? Every tool wrapper generated by `bin/omarchy-mise-install` (claude, codex, gemini, copilot, opencode, gh, pi, ghui, hunk, playwright…) can enter an infinite loop that repeatedly prints the `mise use` line and never launches the tool. **Root cause.** The generated wrapper (`~/.local/bin/$command`) is: ```bash #!/bin/bash mise use -g "$package" exec "$bin" "$@" ``` `exec "$bin"` resolves `$bin` **by name through PATH**. When `$command == $bin` (e.g. `claude`→`claude`) and `~/.local/bin` sits **before** mise's `installs/<tool>/latest` in PATH, `exec "$bin"` re-finds the wrapper itself → runs `mise use -g` again → execs itself again → infinite loop. Each iteration prints the mise line, which is the visible symptom. **Why it hits stock installs.** mise keeps `installs/<tool>/latest` ahead of `~/.local/bin` via `_mise_hook` in `PROMPT_COMMAND`. Per #3685, starship/zoxide (omarchy defaults) overwrite `PROMPT_COMMAND` and drop `_mise_hook`, so the prepend stops. Ordinary tools then fall back to system versions (#3685's complaint), but these wrappers **infinite-loop** instead. Also reachable transiently at fresh-shell startup before the first prompt hook fires. **Steps to reproduce.** ```bash # state where mise hasn't prepended the install dir PATH="$HOME/.local/bin:$HOME/.local/share/mise/shims:/usr/bin:/bin" claude ``` It spins forever, printing this line on every iteration and never launching the tool: ``` mise ~/.config/mise/config.toml tools: [email protected] mise ~/.config/mise/config.toml tools: [email protected] mise ~/.config/mise/config.toml tools: [email protected] ... (~28 iterations in 3s before `timeout` kills it with exit code 124) ``` Workaround: run any `mise` command first so the hook re-prepends the install dir. **Suggested fix** (keeps lazy install; correct regardless of PATH ordering; scoped to the one package so it doesn't leak other runtimes (node/java/etc.) into the tool's PATH): ```bash mise use -g "$package" exec mise exec "$package" -- "$bin" "$@" ``` Verified against all affected wrappers. PR incoming.
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.