github patrickjaja/claude-desktop-extra v3.6556.2
Claude Desktop 3.6556.2

2 hours ago

Claude Desktop 3.6556.2

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

Installation Options

Arch Linux (pacman Repository - recommended)

curl -fsSL https://patrickjaja.github.io/claude-desktop-extra/install-pacman.sh | sudo bash
sudo pacman -Syu claude-desktop-extra

Arch Linux (manual package)

# x86_64
sudo pacman -U https://github.com/patrickjaja/claude-desktop-extra/releases/download/v3.6556.2/claude-desktop-extra-3.6556.2-1-x86_64.pkg.tar.zst
# ARM64
sudo pacman -U https://github.com/patrickjaja/claude-desktop-extra/releases/download/v3.6556.2/claude-desktop-extra-3.6556.2-1-aarch64.pkg.tar.zst

Debian/Ubuntu (APT Repository — recommended)

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

Debian/Ubuntu (manual .deb)

# x86_64
sudo apt install ./claude-desktop-extra_3.6556.2-1_amd64.deb
# ARM64
sudo apt install ./claude-desktop-extra_3.6556.2-1_arm64.deb

Fedora/RHEL (RPM Repository — recommended)

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

Fedora/RHEL (manual .rpm)

# x86_64
sudo dnf install ./claude-desktop-extra-3.6556.2-1.x86_64.rpm
# ARM64
sudo dnf install ./claude-desktop-extra-3.6556.2-1.aarch64.rpm

NixOS / Nix

nix run github:patrickjaja/claude-desktop-extra

AppImage (Any Distro)

# x86_64
chmod +x Claude_Desktop-3.6556.2-x86_64.AppImage
./Claude_Desktop-3.6556.2-x86_64.AppImage
# ARM64
chmod +x Claude_Desktop-3.6556.2-aarch64.AppImage
./Claude_Desktop-3.6556.2-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
Arch pacman (x86_64) 4c451dca804da7106d0fd0d053db46be81d3dd009a85194511f633c608e47e73
Arch pacman (aarch64) a0b7398882ad2672901c475dd8ca00358b3a14f2395872c2335ba790b284960a
Tarball (x86_64) 15d9e5d164ae471d76d1e558efae2241b168fd4d7de2838c946832652ab6727f
Tarball (aarch64) 1864ec76103045e8f8a2b2ad3311586bc9bf9e0bf3caf3402d25870d2b755bf5
AppImage (x86_64) a1e798cce6c3b1dcd8e40cfb5670840bb88fdb94e9e39402d799c7648d2c3fa8
AppImage (aarch64) 4efb1bd7ae70abeab284a4a42c99901405175ffc926603c6149a58d366065fdc
Debian (amd64) df81ecb9699662e0007753da6195fec2d0c4d101c1b290de9b84c9be4d69ca1a
Debian (arm64) 2edd0b3137bc6d61ac73f1b48914fdb0d02dccd3e7d4db4a67a593b9ac722d1c
RPM (x86_64) 288d045760046581120ee850b758e22644d719915800a362875690cdfa638d8d
RPM (aarch64) d303534e43026b3967ebe0620ca1325ab64391f59744687695cd6d9b51659d81

Changes since last release

From CHANGELOG.md, 2026-10-23:

Claude Desktop v3.6556.2

  • Rebased on the official v3.6556.2 .deb (bundled Electron 44.9.3). Three patches were re-fitted to
    the new code; none of them was absorbed upstream:
    • add_feature_files_quick_open.nim: the worker host now has a per-worker env option, which only the
      new frame-local worker sets. Main's live environment is now inserted ahead of that option, so a
      worker's own env still takes precedence. The file-index and heavy-work workers again receive
      CDB_FILES_QUICK_OPEN and CDB_TRANSCRIPT_LIMITS.
    • fix_marketplace_linux.nim: upstream's local-plugin reader now sorts entries into plugins and
      "other folder" plugins. Personal plugins, which the CLI stores as project scope on $HOME, again list
      under Personal Plugins.
    • fix_update_check_own_releases.nim: the Linux updater init now also starts a restart-enforcement
      ticker. The update-link hook still runs before the poll.
  • Extra -> Deployment lists upstream's new managed-settings keys: installedUpdateEnforcementEnabled
    and installedUpdateEnforcementHours, plus quickEntryScreenshotsEnabled and
    quickEntryFileSharingEnabled, which only the macOS Quick Entry reads. toolPolicyEndpoint, which
    upstream removed, is gone (196 keys).
  • The GrowthBook override template covers the 17 new flags (635 entries).

Computer Use on GNOME Wayland: consent dialog on every action, no restore token, screens timing out (#293)

Three defects in gnome-portal-bridge (github.com/patrickjaja/gnome-bridge), present since its first release:

  • Monitor enumeration never reached Mutter. The bridge's decoder for org.gnome.Mutter.DisplayConfig.GetCurrentState was one field short of Mutter's mode signature, and zbus rejects the whole reply on a mismatch, so screens always fell back to opening a fresh portal session. That is the consent dialog behind screens, and because every pointer and capture command resolves its monitor the same way, a dialog per click and per zoom too, daemon or not. It is also why claude-desktop --diagnose reported screens timing out and why the ids were stream-116 instead of connector names. Fixed, with a unit test pinning the decoder to Mutter's published signature; screens now answers in milliseconds.
  • No restore token was ever stored. The portal only accepts persistence for a combined RemoteDesktop + ScreenCast session through RemoteDesktop.SelectDevices; the library the bridge used asked on ScreenCast.SelectSources as well, the portal refused, and the bridge retried without persistence on every GNOME version. The bridge now builds the session itself and requests persistence the way the portal specifies. Verified on GNOME 48: after the first grant, sessions and one-shot commands run with no dialog.
  • session-end could leave serve-session running (and the screen-sharing indicator on). The daemon now records its pid, session-end waits for it and escalates to SIGTERM and SIGKILL, the daemon bounds its own teardown, and a client killed mid-request (the executor's timeout) no longer takes the daemon down with it. Its stderr goes to $XDG_RUNTIME_DIR/gnome-portal-bridge/daemon.log.

On top: zoom without --display (the executor's fallback when it has no monitor list) now takes global coordinates and clamps the region to the display instead of refusing it on a monitor not at the origin, and the executor no longer caches a failed screens enumeration for the whole process (it retries after 30 s), so one slow reply cannot pin every later capture to global coordinates. The GNOME lifecycle harness covers the retry. Operator notes: in the consent dialog keep "Remember This Selection" on and turn on "Allow Remote Interaction"; gnome-portal-bridge doctor reports restore_token_present.

Links

Don't miss a new claude-desktop-extra release

NewReleases is sending notifications on new releases.