patrickjaja/claude-desktop-extra v4.23118.1-5

Claude Desktop 4.23118.1 (patch release 5)

on GitHub

Claude Desktop 4.23118.1 (patch release 5)

This release provides Claude Desktop version 4.23118.1 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/v4.23118.1-5/claude-desktop-extra-4.23118.1-5-x86_64.pkg.tar.zst
# ARM64
sudo pacman -U https://github.com/patrickjaja/claude-desktop-extra/releases/download/v4.23118.1-5/claude-desktop-extra-4.23118.1-5-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_4.23118.1-5_amd64.deb
# ARM64
sudo apt install ./claude-desktop-extra_4.23118.1-5_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-4.23118.1-5.x86_64.rpm
# ARM64
sudo dnf install ./claude-desktop-extra-4.23118.1-5.aarch64.rpm

NixOS / Nix

nix run github:patrickjaja/claude-desktop-extra

AppImage (Any Distro)

# x86_64
chmod +x Claude_Desktop-4.23118.1-x86_64.AppImage
./Claude_Desktop-4.23118.1-x86_64.AppImage
# ARM64
chmod +x Claude_Desktop-4.23118.1-aarch64.AppImage
./Claude_Desktop-4.23118.1-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

Changes since last release

From CHANGELOG.md, 2026-11-10:

Computer Use from cloud Cowork and Dispatch on Wayland, truthful access descriptions, an opt-in Escape stop key (#323)

• Computer Use over the device bridge (cloud Cowork, chats linked to this computer, Dispatch) works on a Wayland session with a bundled bridge: the computer tools are announced, calls are no longer refused with "needs an Xorg session", and the approval card shows app icons. If you turn the background display off while the app runs and no bundled bridge remains usable, Computer Use calls from cloud Cowork and Dispatch are refused on that session until the app restarts (the tool list may still show the tools until Anthropic's code next refreshes it).
• What Claude is told about access now follows the active backend: the local Cowork system-prompt note, the per-app access capability (Settings -> Computer use and the enable dialog), the enable-prompt approval card and the "Entire screen" choice. Per-app access is reported on KDE Plasma, X11, sway and Hyprland (masking; popups and layer-shell surfaces can still show) and the background display, and not on GNOME, niri, river or the fallback tools, nor when Ask before Computer Use controls an app is off (KDE Plasma excepted). See Computer Use.
• Teach mode works on KDE Plasma Wayland and follows the account's teach-mode setting; X11 is unchanged.
• New opt-in switch Escape stops Computer Use (Settings -> Extra -> Community Features and the Extra -> Computer Use page, off by default): Escape stops Computer Use while Claude is working on X11 and Hyprland (Escape still reaches your apps), sway and KDE Plasma Wayland (Escape is taken while Claude is working); GNOME and niri have no stop key. Off keeps Anthropic's own Escape handling. The bundled x11-bridge, wlroots-bridge and kwin-portal-bridge gain an abort-watch subcommand; claude-desktop --diagnose prints an abortWatch line per bridge. See Escape stops Computer Use.
• Stop sharing on the GNOME or KDE screen-share indicator now stops the running Computer Use turn at once; so does the desktop ending the share itself (for example a portal restart). An Escape that Claude itself presses is no longer taken for yours by Anthropic's X11 Escape handler.
• wlroots-bridge sends Escape, modifiers and US-layout keys at their standard key codes, so compositors that match bindings by key code (Hyprland) no longer see every injected key on one code, and Shift combos deliver the shifted symbol (shift+a types A, shift+tab is back-tab).
• Cowork's "install QEMU" hint names your distro's own packages: dnf on Fedora and the RHEL family, pacman on Arch, zypper on openSUSE, a NixOS hint; Debian, Ubuntu and image-based Fedora variants (Silverblue, Kinoite, Bazzite) keep Anthropic's text (new patch fix_cowork_install_hint_linux). In Settings -> Extra -> Deployment, claudeInChromeEnabled notes that Anthropic's Linux build reports it as not supported.
• The Computer Use access patch no longer touches the OS-permission step: upstream reports it granted on Linux itself.
• New build gates: a predicate census and a refusal-string census run after patching (local builds and CI), so an upstream release that adds a Linux/Wayland decision or a refusal string on a strong topic our patches do not cover fails the build instead of shipping; weaker findings are warnings that the update workflow turns into failures with --strict. See Census gates.

Follow-ups: tools installed while the app runs, local-build bridges, release pipeline

• Computer Use picks up a tool installed, or ydotoold started, while Claude Desktop is running: a "not found" is re-checked after 5 seconds instead of lasting until restart.
• Local builds (build-local.sh) check every bundled Computer Use bridge against its glibc floor. A pre-built gnome or kwin bridge above glibc 2.39 (built on a rolling distro) is rebuilt in an ubuntu:24.04 container as CI does, cached per checkout state; without docker the build warns and bundles the host binary, or fails with --strict-bridges. The build log names each bridge's source and glibc requirement.
• The launcher no longer expands glob characters in XDG_DATA_DIRS / FONTCONFIG_PATH entries.
• Release pipeline: the Pages deployment gets a longer timeout and one automatic second attempt, and the package test containers retry apt-get when a mirror is briefly out of step.

Tools the app runs itself are found again under upstream's PATH narrowing (4.23118+)

• Claude Desktop 4.23118 narrows its own PATH to system folders at startup. A new shared lookup (add_tool_path_resolver) lets our patches find the tools they run in those system folders plus the root-owned read-only folders of the PATH Claude Desktop was started with, by absolute path; a copy in a folder your user can write to is never used and is named in claude-patches.log.
• RHEL 9 / Rocky / Alma: local Cowork finds qemu-kvm through the package's qemu-shim again instead of reporting "Cowork requires QEMU".
• Where xdg-open is not installed in a system folder but comes from a root-managed one (as with the Nix package's own xdg-utils), links, "Open in ..." and sign-in open again (fix_open_external_tool_path); where xdg-open is in a system folder nothing changes. "Open in VS Code / Cursor / ..." and the Chrome DevTools opener find xdg-mime / xdg-open the same way.
• Quick Entry placement (hyprctl), Chrome cookie import (secret-tool, kwallet-query) and local Cowork's QEMU also use tools from root-managed folders such as /etc/profiles/per-user/<you>/bin. Diff views find git on the PATH Claude Desktop was started with, as the app's own Code sessions do.
• The background-display setup page checks the clipboard tools where Computer Use looks for them. claude-desktop --diagnose prints the folders tools are taken from and names a tool found only in a user-writable folder. See Troubleshooting.
• Upstream 4.23118.1 audited against 4.23118.0: a point fix (Windows program lookup, an NFS rename retry on Linux), no flag, gate or IPC change; baselines re-stamped, and flag 1358805273 is documented as the PATH-narrowing kill switch.

Named profiles get their own window identity (#319)

• A named profile's windows now carry Wayland app_id / X11 WM_CLASS com.anthropic.Claude-<name> when the profile's com.anthropic.Claude-<name>.desktop exists in the XDG applications directories, so desktops that match windows to .desktop entries can show each profile as its own entry (Claude (work)); give the profile's .desktop its own Icon= to tell them apart at a glance (new patch fix_profile_app_identity). A profile without that file (--profile=NAME without --create-profile) keeps the shared com.anthropic.Claude identity. The default profile is unchanged; window rules written for com.anthropic.Claude do not match a named profile's windows, notifications are still attributed to the default app entry, and the claude:// handler stays with the default profile. On KDE Plasma a named profile now registers the Quick Entry shortcut under its own entry (Claude (work)), so Plasma asks once per profile to confirm the shortcut on the first launch after the update.
• Quick Entry swaps its own app id in only around its window's construction and restores the previous value right after, so windows opened later always carry the main identity, also when Quick Entry was built but not yet shown.
• Per-profile .desktop files written by --create-profile now set StartupWMClass=com.anthropic.Claude-<name>, and existing launcher-written profile files are updated on the next launch. The AppImage's named-profile entry starts that profile and no longer claims the claude:// handler (an entry from an older version hands it back to the default entry). claude-desktop --diagnose states which window identity a profile uses.
• In a named profile, Computer Use treats only that profile's own windows as the Claude host; other profiles' Claude windows are ordinary apps to it.

Computer Use: apps installed per user launch again (thanks @aenriii, #321)

• Claude Desktop 4.23118 narrows its own PATH to system folders at startup, so an app whose launcher names a program in a per-user folder (~/.local/bin, a home-manager or Nix profile) read as "command not found" when Computer Use opened it. Apps are now found and started with the PATH Claude Desktop was launched with, on the background display and on your desktop.
• The tools Computer Use runs itself (setsid, clipboard tools, desktop launcher tools, ydotool, spectacle) are taken from the system folders and from root-managed read-only folders on that PATH only, by absolute path; a copy in a folder your user can write to is ignored and named in claude-patches.log. On NixOS this finds the tools the package wrapper and the system or per-user profile provide. URLs and files open through the system xdg-open. See Computer Use.

NixOS: a background display for Claude (thanks @aenriii, #322)

• New option programs.claude-desktop-extra.backgroundDisplay in nixosModules.default: a headless sway for one user as a systemd user service (claude-extra-display), started at boot through lingering, on a private D-Bus and under a stable socket name (wayland-claude-extra) for Computer Use on a background display. It can also run a Chromium-family browser with its own profile and the Claude in Chrome native-messaging manifest, with a gnome-keyring unlocked by a password sealed with systemd-creds. Viewing it over VNC is opt-in (vnc.enable, or vnc.unixSocket for a socket only your user can reach). Everything is off unless enable = true. See docs/nixos-background-display.md.
• Settings -> Extra -> Cowork (Linux) -> Computer Use on a background display lists a stable-name link to a compositor socket, so wayland-claude-extra can be picked there.

Links

• Full Changelog