patrickjaja/claude-desktop-extra v4.23118.0

Claude Desktop 4.23118.0

on GitHub

Claude Desktop 4.23118.0

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

NixOS / Nix

nix run github:patrickjaja/claude-desktop-extra

AppImage (Any Distro)

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

Changes since last release

From CHANGELOG.md, 2026-11-05:

Claude Desktop 4.23118.0

• Updated to upstream 4.23118.0 (Electron 44.9.3). Re-fitted four patches to the new minified bundle: Computer Use's executor injection (upstream's macOS executor now takes an options object), the session-start dialog, the auto-archive delay and the renderer-gone log. The session-start and auto-archive patches now take upstream's function names from upstream's own call sites, so a rename no longer breaks them.
• Extra -> Deployment lists the new managed setting allowManagedHooksOnly; organizationPluginsUrl is gone upstream and was removed from the list. The GrowthBook override catalog covers the 777 flags of this version.

Community Features grouped by where they apply

• Settings -> Extra -> Community Features now groups its rows under Code (with a Pull requests subgroup), App and window and Models and 3P. Each row starts with one sentence on what it does; search still matches every detail. The Extra headline in the settings sidebar now has a slowly moving rainbow (static when the system asks for reduced motion).

PR auto-archive delay: remaining time and keep button in 3P mode (thanks @alexx-ftw, #316)

• In 3P mode, with a nonzero PR auto-archive delay, a line below upstream's auto-archive hold notice shows the time left on a merged or closed PR's delay, and the session rail offers Keep this session, which turns off upstream's per-session "Auto-archive on merge or close". The delay itself works in both 1P and 3P mode. With the delay at Immediately, upstream's UI is unchanged.

Clearer patch placement guidance and corrected Auto-fix notice docs (thanks @alexx-ftw, #315)

• AGENTS.md and docs/patches.md now say where a patch belongs: core/ only for shared plumbing, a fix serving an optional feature stays in that feature's patch behind its switch, tested with the switch on and off. The Auto-fix notice docs now match the shipped behavior (REST read spacing and backoff, direct vs queued delivery, budget-skip handling, text normalization), and docs/patches.md no longer claims a byte-identical install tree or that a green build proves runtime behavior.

Auto-fix notices are confirmed in batched turns (thanks @alexx-ftw, #314)

• With Settings -> Extra -> Community Features -> "Auto-fix notices: ready to merge, comments after merge" on, a ready-to-merge or post-merge notice that Claude reads later in a turn covering several queued messages is now confirmed when that turn completes, instead of staying pending (upstream confirms only the turn's first message). Unread, withdrawn and next-cycle messages are not confirmed.

Session-start dialog for explicit local folders (thanks @alexx-ftw, #313)

• The opt-in native session-start dialog now also covers an explicit local folder, showing its resolved directory; the first-use folder consent is answered there too. Approvals are kept per asking project and folder, but upstream tracks first use in memory, so a new asking session or an app restart asks again for that folder; the default destination stays remembered as before. A PreToolUse ask hook may be answered in the dialog instead of the card (the person is still asked); user ask rules and managed policy keep the card. Manual-mode asks for a new folder (upstream's ordinary card, without the folder sentence) now reach the dialog too, and an ask that keeps the card logs [session-start-always-allow] card kept: <reason> to claude-patches.log.

Auto-fix forwards comments that arrive after a merge (thanks @alexx-ftw, #310)

• After an Auto-fix PR is merged, new comments, inline review comments and reviews from the repository's owners, members, collaborators and bots reach its Code session as quoted informational notices for 7 days after the merge (mentions defanged, each text capped at 1200 characters; upstream stops reading a PR once it is merged). Claude reports them and waits for you: it never changes code, replies on GitHub or merges. Archived sessions are not read or woken. Same switch as the ready-to-merge notice, now titled Settings -> Extra -> Community Features -> "Auto-fix notices: ready to merge, comments after merge" (off by default, applies live).
• Cost: per Auto-fix PR inside its window, one round of ETag-conditional GitHub REST reads per sweep (the PR and its three comment lists), none while fewer than 1000 REST requests remain or a rate-limit window is open; one model turn per notice. Details: docs/autofix-post-merge.md.

Auto-archive delay after a PR merges or closes (thanks @alexx-ftw, #311)

• New row Settings -> Extra -> Community Features -> "Auto-archive delay after a PR merges or closes": Immediately (the default, upstream's behavior), 5, 15, 30 or 60 minutes, or a custom 1-10080 minutes. After upstream confirms a session's PR merged or closed, its auto-archive waits that long. The deadline survives restarts, and a confirmed reopen cancels it. It does not turn auto-archive on, and the inactivity rule is unchanged.
• Expiry is checked on upstream's 5-minute archive sweep, so the archive lands within about 5 minutes of the deadline. During the delay the session skips upstream's GitHub re-reads and worktree checks (a close upstream could not confirm yet is still confirmed first); when it ends, every upstream check and hold still applies. Details: docs/auto-archive-grace.md.

A native dialog with "Allow always" for starting other sessions (thanks @alexx-ftw, #312)

• New switch Settings -> Extra -> Community Features -> "Native dialog with 'Allow always' for starting other sessions" (off by default = upstream's in-chat card, applies live). When Claude asks to start another Code session, a dialog on the app window offers Deny (the default), Allow once and Allow always, and shows the session title, project, destination, permission mode, model and the start of the prompt Claude wrote.
• Allow always is remembered for that project and its default destination only: another folder, host, environment, preset, the cloud or a higher permission mode still asks, and nothing inside the new session is approved by it. The row shows how many projects are remembered and forgets them; switching it off forgets them too. Details

Links

• Full Changelog