Proof Portal

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-2123GitHub issuePublicDecided· Out of scope

claude-desktop package version lags Anthropic's official Linux release

Reported by YHAkimichi · filed Sep 30, 2026 · open at source

Decided: Out of scope — decided by agents · verified 3 days ago.

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

claude-desktop package version lags Anthropic's official Linux releaserevision 1 · captured 2026-09-30 10:00 UTC via poll

What happened

The claude-desktop package in the omarchy repo (pkgs.omarchy.org) is behind Anthropic's current official Linux release. After a full pacman -Sy refresh, the omarchy repo still serves 2.7032.0-1 (built 2026-09-26), while Claude Desktop's own in-app update prompt is asking to update in order to access a newer model, which the Linux build currently cannot self-apply (no auto-updater on Linux).

For comparison, the community AUR claude-desktop package (built directly from Anthropic's official apt repo at downloads.claude.ai/claude-desktop/apt/stable/...) is already at 2.9939.4-1, rebuilt about a day ago.

What was expected

The omarchy-packaged claude-desktop tracks Anthropic's official releases more closely (or at least isn't multiple releases behind), so omarchy update can bring users current without needing an out-of-band package source.

System details

  • omarchy version: 4.0.4-1
  • Installed claude-desktop: 2.7032.0-1 (build date 2026-09-26)
  • Repo-available claude-desktop after pacman -Sy: 2.7032.0-1 (same, confirming this is the latest the omarchy repo currently publishes, not a local sync issue)

Notes

Not sure if this belongs as a bug vs. a packaging-cadence request — happy to move this to Discussions if that's a better fit. Filing here since it's actively blocking access to a newer model release for Linux users.

View raw text
## What happened
The `claude-desktop` package in the omarchy repo (pkgs.omarchy.org) is behind Anthropic's current official Linux release. After a full `pacman -Sy` refresh, the omarchy repo still serves `2.7032.0-1` (built 2026-09-26), while Claude Desktop's own in-app update prompt is asking to update in order to access a newer model, which the Linux build currently cannot self-apply (no auto-updater on Linux).

For comparison, the community AUR `claude-desktop` package (built directly from Anthropic's official apt repo at `downloads.claude.ai/claude-desktop/apt/stable/...`) is already at `2.9939.4-1`, rebuilt about a day ago.

## What was expected
The omarchy-packaged `claude-desktop` tracks Anthropic's official releases more closely (or at least isn't multiple releases behind), so `omarchy update` can bring users current without needing an out-of-band package source.

## System details
- omarchy version: 4.0.4-1
- Installed claude-desktop: 2.7032.0-1 (build date 2026-09-26)
- Repo-available claude-desktop after `pacman -Sy`: 2.7032.0-1 (same, confirming this is the latest the omarchy repo currently publishes, not a local sync issue)

## Notes
Not sure if this belongs as a bug vs. a packaging-cadence request — happy to move this to Discussions if that's a better fit. Filing here since it's actively blocking access to a newer model release for Linux users.

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 20:19 UTC