Claude Desktop 1.18286.0

Claude Desktop 1.18286.0

This release provides Claude Desktop version 1.18286.0 pre-patched for Linux.

Installation Options

Arch Linux (AUR)

yay -S claude-desktop-bin

Debian/Ubuntu (APT Repository — recommended)

curl -fsSL https://patrickjaja.github.io/claude-desktop-bin/install.sh | sudo bash
sudo apt install claude-desktop-bin

Debian/Ubuntu (manual .deb)

# x86_64
sudo apt install ./claude-desktop-bin_1.18286.0-1_amd64.deb
# ARM64
sudo apt install ./claude-desktop-bin_1.18286.0-1_arm64.deb

Fedora/RHEL (RPM Repository — recommended)

curl -fsSL https://patrickjaja.github.io/claude-desktop-bin/install-rpm.sh | sudo bash
sudo dnf install claude-desktop-bin

Fedora/RHEL (manual .rpm)

# x86_64
sudo dnf install ./claude-desktop-bin-1.18286.0-1.x86_64.rpm
# ARM64
sudo dnf install ./claude-desktop-bin-1.18286.0-1.aarch64.rpm

NixOS / Nix

nix run github:patrickjaja/claude-desktop-bin

AppImage (Any Distro)

# x86_64
chmod +x Claude_Desktop-1.18286.0-x86_64.AppImage
./Claude_Desktop-1.18286.0-x86_64.AppImage
# ARM64
chmod +x Claude_Desktop-1.18286.0-aarch64.AppImage
./Claude_Desktop-1.18286.0-aarch64.AppImage

Update existing AppImage (delta download — only changed blocks):

appimageupdatetool Claude_Desktop-*-x86_64.AppImage
# Or from within the AppImage:
./Claude_Desktop-*-x86_64.AppImage --appimage-update

Checksums

File	SHA256
Tarball (x86_64)	ab5ae9d31a133ad4e5458cd7e9b178489491a6ae93c5dbf40b7199185484015f
Tarball (aarch64)	f1782ef6f7dc7ecc2bb8f9e87865c9a75df9cbc8e52166c62c4d99c77ae73661
AppImage (x86_64)	6dc90e323ac362814a5e10b44ee39d9fe6c1c717980c6b7e21f3cf15ccfd2970
AppImage (aarch64)	39b6b524db0d6e9ec2d6e98b4af922ee6e407dfdfde746fb7b401c0599ee431c
Debian (amd64)	c3f5face1307c89e09ab88f52e18f76e5fb969c2ea6baa3ec822e7844c620e73
Debian (arm64)	9d0f6acdc00737b09e4979851ae231f80194236527e22360043469e1244a45df
RPM (x86_64)	ce630e58756bfab50915397c8c5375ce3ff6841e247ed0138fa356fafd00a61b
RPM (aarch64)	b32f0e8938c8490ade82dbbb7ed72a3ff0a635237437a319d817f3160624311f

Changes since last release

Upstream bump v1.17377.2 -> v1.18286.0: three patches re-anchored after the auto-release failed

The 2-hourly version check dispatched an auto-release for v1.18286.0 and it failed (tracking issue #176). The bump is a full re-minify plus a few small refactors; three patches needed work:

• enable_local_agent_mode: GrowthBook flag 1496676413 (SSH remote MCP/plugin passthrough) was removed upstream - the feature went unconditional (createSpawnFunction lost the flag argument, resolveSshControllerForMcp returns the controller whenever an sshConfig exists). Patch 3n deleted (19/19 sub-patches), with a guard that fails the build if the flag ever reappears.
• fix_buddy_ble_linux: the Buddy flag gate gained a new workspace.hardwareBuddyEnabled setting in its chain (upstream's new Cowork "Hardware Buddy & Maker Devices" BLE feature). Re-anchored so only the GrowthBook half is forced - the user's hardwareBuddyEnabled toggle keeps working.
• fix_computer_use_linux: upstream re-shaped the CU enable gates - the old isEnabled/rj pair merged into a wS() (pref-respecting) / bue() (flag-gated, pref-ignoring) / dq() (stub-mode nudge) family, the handleToolCall body was extracted into vgn() with teach-mode telemetry, and the tool wrapper gained an abort timeout. Patches 5b/6/11/12 re-anchored: wS gets the Linux pref-respecting branch, bue delegates to the patched wS on Linux (so a remote flip of its gating flag can't switch CU back off), and dq stays untouched (false on Linux keeps the "enable in settings" nudge path off). CI only reported 2 of the 4 - Patch 6's abort-on-failure had masked the downstream 11/12 failures. 36/36 sub-patches apply; a live Computer Use smoke-test after install is recommended since the handler was restructured.

Audits came back clean: platform-gate counts byte-identical (darwin 78 / win32 128 / linux 12 - no new PORTABLE opportunities, no new Linux blockers), the Cowork VM capability probe is structurally unchanged, resources identical (no new binaries), IPC additions purely additive (Claude Code PR/CLI-status channels, CU remote-lock release, file-preview open-in-default-app), ion-dist patch applies unchanged, GrowthBook +8/-4 with nothing needing forcing. Official docs (code.claude.com/docs/en/desktop-linux) still list Computer Use as not available on Linux - our CU stack remains the only one. Baseline docs updated (CLAUDE_FEATURE_FLAGS.md renames sM()/Yue/rt() + history row, PLATFORM_GATE_BASELINE.md, ION.md).

@boommasterxd independently root-caused and fixed the same three patches in PR #179 (merged) - both analyses agreed on every root cause. Where the approaches differed, the stricter/pref-preserving variant won: his resolveSshControllerForMcp regression guard and the \6 setTimeout backref were adopted; our ternary-anchored CU gate patches (which keep the chicagoEnabled user pref working for tool listing) and the toggle-respecting Buddy anchor were kept.

NixOS Cowork "requires QEMU" while --diagnose passes: root-caused, diagnose false-positive fixed, env overrides added (#177)

On NixOS the in-app probe failed on virtiofsd while claude-desktop --diagnose claimed the capability probe "SHOULD pass". Two distinct bugs:

• --diagnose false positive: the launcher listed the bundled resources/locales/virtiofsd as an unconditional candidate, but the app only uses the bundled copy on Ubuntu 22.x (/etc/os-release gate) - on every other distro a missing system virtiofsd means virtiofsdPath=null and the "Cowork requires QEMU ... virtiofsd" message. The diagnose replica now mirrors the Ubuntu-22 gate and prints an actionable NOT-FOUND hint instead.
• No way to point the probe anywhere on NixOS: the probe's candidate lists are fixed /usr/... paths that NixOS never populates. fix_cowork_firmware_paths_linux now prepends two env-var overrides to the probe arrays (conditional spreads, no-ops when unset): CLAUDE_VIRTIOFSD_PATH and CLAUDE_OVMF_CODE_PATH (CODE image; the VARS sibling is derived by name next to it). Injected into both the x86_64 OVMF and arm64 AAVMF arms (3 sub-patches, strict).

The Nix package now resolves virtiofsd and OVMF from nixpkgs automatically (like qemu) and wires them via those env vars - Cowork on NixOS needs no tmpfiles symlink hacks from this release on. README and package.nix notes corrected: they previously claimed "virtiofsd is bundled" and omitted the system-virtiofsd requirement entirely; the Cowork setup section now documents it for all non-Ubuntu-22 distros, plus the new env overrides.

Independently root-caused and fixed in parallel by @boommasterxd (PRs #178 and #179, merged) - both analyses agreed on the Ubuntu-22-gate root cause and the diagnose bug. Merged from his PRs on top of the above: the /run/current-system/sw/bin/virtiofsd probe candidate (covers NixOS installs that bypass our Nix wrapper, e.g. AppImage, via pkgs.virtiofsd in environment.systemPackages), the --diagnose hint line when the bundled virtiofsd exists but is correctly ignored, and the stronger enable_local_agent_mode Patch 3n regression guard (asserts resolveSshControllerForMcp stays unconditional instead of only checking the removed flag ID is absent).

Links

• AUR Package
• Full Changelog