Repository navigation
Add claude-desktop, Anthropic's Linux desktop beta - #348
Conversation
Anthropic ships the Claude desktop app for Linux only through its own Debian repository, so the package repacks the deb the way openai-codex-desktop does: extract data.tar.xz, replace the bare /usr/bin symlink with a launcher that asks Chromium for Wayland directly, and keep the vendor copyright as the license. Updates come through the declarative "debian" upstream provider: the apt Packages index names the newest version, and the per-architecture pool debs are hashed when one appears. Verified by pinning 1.44121.2 and watching bin/sync-upstream rewrite it back to 1.46388.2 byte-identically.
|
Reviewed at 0b51b8a, with an independent codex second opinion at xhigh reasoning and build/runtime testing on a disposable Omarchy VM. The packaging and update machinery check out; the Cowork optdepends do not, and that is the one thing blocking this. What was checked. Finding 1 (high): the Cowork optdepends don't deliver Cowork on Arch. The app probes Finding 2 (medium, from codex, verified): no Finding 3 (judgement call): the launcher doesn't pin Rejected: codex flagged the flags-file parsing (quoted values with spaces break, Overlap: #274 adds the same package with GPG verification of the signed index from a repo-pinned key, Waiting on: the author for findings 1–2, and the maintainer for the #274 decision and finding 3. 🤖 Generated by Fable 5 in Claude Code. Reviewed by Codex XHigh. |
…andbox deps The app probes Debian's paths for its VM stack: /usr/libexec/virtiofsd then /usr/bin/virtiofsd, and /usr/share/OVMF/OVMF_CODE_4M.fd with the VARS path derived from it. Arch ships virtiofsd at /usr/lib/virtiofsd and the firmware at /usr/share/edk2/x64/OVMF_CODE.4m.fd, so installing the advertised optdepends still left Cowork reporting QEMU missing. Symlinks at the probed paths map them onto Arch's; the app's probe reads through them, they dangle harmlessly until the optdepends arrive, and /usr/libexec keeps the virtiofsd link out of $PATH while it does. The firmware optdepend moves into optdepends_x86_64, and aarch64 loses its Cowork optdepends entirely: the aarch64 builds run against Arch Linux ARM, which ships no UEFI firmware package at all, so both the edk2 name and the qemu-system-aarch64 entry promised a VM that cannot boot there. The embedded Claude Code diagnoses missing sandbox dependencies when bubblewrap and socat are absent; they join the optdepends under the same wording as the standalone claude-code package. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Co-Authored-By: Codex XHigh <noreply@openai.com>
|
Pushed cef906d addressing the review findings, verified on a disposable Omarchy VM with a codex second opinion at xhigh reasoning on the fix diff. What changed. Symlink shims map the Debian paths the app probes onto Arch's — aarch64 lost its Cowork optdepends instead of gaining a firmware one. Codex caught what my first cut of the fix missed: the aarch64 builds run against Arch Linux ARM, and its repos carry no edk2/OVMF/AAVMF package at all (verified against the mirror the builder configures — zero matches in core, extra, alarm, and aur). Evidence, before and after, same VM with every advertised optdepend installed. Under 0b51b8a: Under cef906d:
Codex confirmed the x86_64 shim chain hop-by-hop, the dangling-probe behavior, the per-arch optdepends arrays, and the absence of file conflicts; its one substantive finding was the aarch64 repository gap above, which reshaped the commit. Its style suggestion on the If Omarchy later imports a UEFI firmware package for aarch64, the optdepends and an AAVMF shim can come back in the same shape. 🤖 Generated by Fable 5 in Claude Code. Reviewed by Codex XHigh. |
virtiofsd sat in the common optdepends, so aarch64 still advertised one third of a Cowork stack the package deliberately promises nothing else of there. It joins qemu and the firmware in optdepends_x86_64, and the virtiofsd shim moves under the same branch, so an aarch64 package carries no Cowork pieces at all. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Co-Authored-By: Codex XHigh <noreply@openai.com>
|
Final review of 959fa52 — ready to ship from this review's side. No blockers remain in the package; what is left open is the maintainer's choice against #274 and one judgement call noted at the end. Every check below ran on a disposable Omarchy VM built from the ISO, with an independent codex second opinion at xhigh reasoning as the last gate; codex reviewed cef906d and raised one finding, fixed in 959fa52, then the whole matrix was re-run on the new head. Codex's finding, fixed. Update machinery. Both architectures build. x86_64 natively (167 MB). aarch64 with Cowork paths on x86_64, with the optdepends installed: Dependencies. The body's claim holds: all 36 NEEDED sonames across every ELF in the payload resolve to packages inside the transitive closure (209 packages) of the 16 declared depends, with Runtime, through the desktop entry ( First launch, native Wayland window under Hyprland: Sign In reached: The desktop entry and icon resolve in Omarchy's app launcher: Not blockers, but on the record. Install → AI in the Omarchy menu does not list Claude Desktop — that entry lives in omacom/omarchy and has to land after this package exists: Past the path gates, Cowork checks 🤖 Generated by Fable 5 in Claude Code. Reviewed by Codex XHigh. |
|
Correction to the final review above: the first The package itself is fine. The same commit built and published to edge and stable on the release builder ( So the pattern runs before merge from now on: #388 adds a The review protocol on the omabot side is updated the same way (omacom/omabot#26): for 🤖 Generated by Fable 5 in Claude Code. |




Anthropic ships the Claude desktop app for Linux (beta since June) only through its own Debian repository at
downloads.claude.ai/claude-desktop/apt/stable, for amd64 and arm64. This packages it the wayopenai-codex-desktoppackages the ChatGPT desktop app: extract the deb'sdata.tar.xz, replace the bare/usr/bin/claude-desktopsymlink with a launcher that asks Chromium for Wayland directly (same logic aschatgpt-launcher.sh, with its ownclaude-desktop-flags.conf), keep the vendor copyright as the license, and drop the Debian policy files. The app has no self-updater on Linux, so nothing needs disabling.Updates come through the declarative
debianupstream provider rather than a bespoke hook: Claude's versions (1.46388.2) are already valid Arch pkgvers, so the apt Packages index names the newest release and the two pool debs are hashed when one appears.release_ringisfast, like the other AI desktop apps.Dependencies were mapped from the deb's control stanza and verified against
readelf -don the actual binary — every NEEDED soname is satisfied directly or transitively by the declared depends. Cowork (the VM-backed agent tab) needs QEMU, UEFI firmware and virtiofsd. The app probes Debian's paths for that stack —/usr/libexec/virtiofsd, and/usr/share/OVMF/OVMF_CODE_4M.fdwith the VARS path derived from it — sopackage()ships symlinks mapping them onto Arch's/usr/lib/virtiofsdand/usr/share/edk2/x64/*.4m.fd, dangling harmlessly until the optdepends are installed. Every Cowork optdepend and shim is x86_64-only: Arch Linux ARM, which the aarch64 builds run against, ships no UEFI firmware package, so on that arch there is no VM to promise and the aarch64 package carries no Cowork pieces at all. The embedded Claude Code names bubblewrap and socat as its sandbox dependencies; both are optdepends, matching the standaloneclaude-codepackage.Verified:
bin/sync-upstream claude-desktopround-trip: pinned the PKGBUILD to 1.44121.2, the sync rewrote it to 1.46388.2 byte-identical to the checked-in file, and reports no update when current.makepkgsmoke test ofpackage()against the real amd64 deb: launcher, license, doc/lintian cleanup, the chrome-sandbox setuid bit, and the Cowork shims all come out right; installed alongsideedk2-ovmfandvirtiofsd, every path the app probes resolves to the real file and virtiofsd executes through its shim.com.anthropic.Claude) under Hyprland.--ultra -22, ~3 minutes extra).One known gap, shared with
1password: thedebianprovider reads a single index (binary-amd64) and substitutes that version into both arch URLs. If Anthropic ever lands amd64 before arm64, that sync run fails loudly on the arm64 404 and self-heals on the next run once both are published.openai-codex-desktop's hook handles that race by comparing both indexes; if it shows up in practice here, the fix belongs in the generic provider rather than another bespoke hook.