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.
Claude Code keeps showing "Update available! Run: mise upgrade claude" even when already on the mise-reported latest version
Reported by fizzledieb · filed Sep 18, 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
Environment
- Omarchy: 4.0.4-1
- Claude Code installed via Omarchy's mise integration (omarchy-mise-install claude, aqua:anthropics/claude-code)
- ~/.config/mise/config.toml: claude = "latest"
- mise ls claude reports 2.1.274 ... latest (currently active)
- claude --version → 2.1.274 (Claude Code)
Steps to reproduce
1. Have Claude Code installed via Omarchy's default mise setup.
2. Run mise upgrade claude (or already be on the version mise reports as latest).
3. Open Claude Code.
Expected
No "update available" banner, since the running version matches what mise considers latest.
Actual
Claude Code repeatedly shows a yellow banner on every launch: "Update available! Run: mise upgrade claude" — even though that command has already been run and the installed version matches mise's latest tag exactly.
Notesmise.sh already disables auto_prune specifically because "Upgrades must not delete the version a running process is executing from," suggesting Omarchy is aware of version-tracking edge cases around the mise-managed Claude Code install. This looks like a related but distinct issue: Claude Code's self-update check doesn't seem to correctly recognize the mise-managed install as up to date, causing a persistent false-positive nag.
View raw text
**Environment** - Omarchy: 4.0.4-1 - Claude Code installed via Omarchy's mise integration (`omarchy-mise-install claude`, `aqua:anthropics/claude-code`) - `~/.config/mise/config.toml`: `claude = "latest"` - `mise ls claude` reports `2.1.274 ... latest` (currently active) - `claude --version` → `2.1.274 (Claude Code)` **Steps to reproduce** 1. Have Claude Code installed via Omarchy's default mise setup. 2. Run `mise upgrade claude` (or already be on the version mise reports as `latest`). 3. Open Claude Code. **Expected** No "update available" banner, since the running version matches what mise considers `latest`. **Actual** Claude Code repeatedly shows a yellow banner on every launch: "Update available! Run: mise upgrade claude" — even though that command has already been run and the installed version matches mise's `latest` tag exactly. **Notes** `mise.sh` already disables `auto_prune` specifically because "Upgrades must not delete the version a running process is executing from," suggesting Omarchy is aware of version-tracking edge cases around the mise-managed Claude Code install. This looks like a related but distinct issue: Claude Code's self-update check doesn't seem to correctly recognize the mise-managed install as up to date, causing a persistent false-positive nag.
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 15:41 UTC