Claude Desktop 4.23118.1 (patch release 3)
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-extraArch Linux (manual package)
# x86_64
sudo pacman -U https://github.com/patrickjaja/claude-desktop-extra/releases/download/v4.23118.1-3/claude-desktop-extra-4.23118.1-3-x86_64.pkg.tar.zst
# ARM64
sudo pacman -U https://github.com/patrickjaja/claude-desktop-extra/releases/download/v4.23118.1-3/claude-desktop-extra-4.23118.1-3-aarch64.pkg.tar.zstDebian/Ubuntu (APT Repository — recommended)
curl -fsSL https://patrickjaja.github.io/claude-desktop-extra/install.sh | sudo bash
sudo apt install claude-desktop-extraDebian/Ubuntu (manual .deb)
# x86_64
sudo apt install ./claude-desktop-extra_4.23118.1-3_amd64.deb
# ARM64
sudo apt install ./claude-desktop-extra_4.23118.1-3_arm64.debFedora/RHEL (RPM Repository — recommended)
curl -fsSL https://patrickjaja.github.io/claude-desktop-extra/install-rpm.sh | sudo bash
sudo dnf install claude-desktop-extraFedora/RHEL (manual .rpm)
# x86_64
sudo dnf install ./claude-desktop-extra-4.23118.1-3.x86_64.rpm
# ARM64
sudo dnf install ./claude-desktop-extra-4.23118.1-3.aarch64.rpmNixOS / Nix
nix run github:patrickjaja/claude-desktop-extraAppImage (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.AppImageUpdate 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) | 6084f2449cddb24b768faf858b5ed730b8021451b795646484737ecb40b4b132
|
| Arch pacman (aarch64) | 1be5e0a838c46b5b028f5166504a11facc0fa3873284a8de1ebf2b51f0ec6fa2
|
| Tarball (x86_64) | fb8bcd594e272181281fb009f189917f5555ff7a2bb697959c2af2436093be89
|
| Tarball (aarch64) | e0f1755348f7defd8ec179152dabc41ff681c0af005ec0d44b462115070a2c4b
|
| AppImage (x86_64) | b8049acbbd68cc8f0285c6e810ebe09e3f783a4a22b00408e6b86c1de0cf872a
|
| AppImage (aarch64) | b582b3e1eb7c8617d3d5d209c0531552f8fa0e471cf3e6292507b9f972e5e6ad
|
| Debian (amd64) | ed0b8c6714cd3638d64018ce3f603b12989a810d60e5977c38c9bc04012a3705
|
| Debian (arm64) | df80c4717639a516cb302d9ba3cb8bb521996d176e973b9922055e41d84d0b00
|
| RPM (x86_64) | db81882296b40b30c48197502004538b2e13459ba89ca7056cb3f3202009e9db
|
| RPM (aarch64) | a6589c40679489a87760de704db36906e10dd4e8599558538f049a9bdf518869
|
Changes since last release
From CHANGELOG.md, 2026-11-10:
Tools the app runs itself are found again under upstream's PATH narrowing (4.23118+)
- Claude Desktop 4.23118 narrows its own
PATHto 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 thePATHClaude Desktop was started with, by absolute path; a copy in a folder your user can write to is never used and is named inclaude-patches.log. - RHEL 9 / Rocky / Alma: local Cowork finds
qemu-kvmthrough the package's qemu-shim again instead of reporting "Cowork requires QEMU". - Where
xdg-openis not installed in a system folder but comes from a root-managed one (as with the Nix package's ownxdg-utils), links, "Open in ..." and sign-in open again (fix_open_external_tool_path); wherexdg-openis in a system folder nothing changes. "Open in VS Code / Cursor / ..." and the Chrome DevTools opener findxdg-mime/xdg-openthe 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 findgiton thePATHClaude 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 --diagnoseprints 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
1358805273is 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'scom.anthropic.Claude-<name>.desktopexists in the XDG applications directories, so desktops that match windows to.desktopentries can show each profile as its own entry (Claude (work)); give the profile's.desktopits ownIcon=to tell them apart at a glance (new patchfix_profile_app_identity). A profile without that file (--profile=NAMEwithout--create-profile) keeps the sharedcom.anthropic.Claudeidentity. The default profile is unchanged; window rules written forcom.anthropic.Claudedo not match a named profile's windows, notifications are still attributed to the default app entry, and theclaude://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
.desktopfiles written by--create-profilenow setStartupWMClass=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 theclaude://handler (an entry from an older version hands it back to the default entry).claude-desktop --diagnosestates 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
PATHto 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 thePATHClaude 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 thatPATHonly, by absolute path; a copy in a folder your user can write to is ignored and named inclaude-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 systemxdg-open. See Computer Use.
NixOS: a background display for Claude (thanks @aenriii, #322)
- New option
programs.claude-desktop-extra.backgroundDisplayinnixosModules.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 withsystemd-creds. Viewing it over VNC is opt-in (vnc.enable, orvnc.unixSocketfor a socket only your user can reach). Everything is off unlessenable = 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-extracan be picked there.