patrickjaja/claude-desktop-bin v1.14271.0-5

Claude Desktop 1.14271.0 (patch release 5)

on GitHub

Claude Desktop 1.14271.0 (patch release 5)

This release provides Claude Desktop version 1.14271.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.14271.0-5_amd64.deb
# ARM64
sudo apt install ./claude-desktop-bin_1.14271.0-5_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.14271.0-5.x86_64.rpm
# ARM64
sudo dnf install ./claude-desktop-bin-1.14271.0-5.aarch64.rpm

NixOS / Nix

nix run github:patrickjaja/claude-desktop-bin

AppImage (Any Distro)

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

Fix: no window opens on Wayland (Vulkan incompatible with --ozone-platform=wayland)

• The launcher now passes --disable-features=Vulkan on native Wayland sessions. On GPUs where Chromium (Electron 42) brings up Vulkan - real Intel/AMD/NVIDIA with a recent Mesa driver - it refuses to pair Vulkan with --ozone-platform=wayland, so the Wayland surface factory fails (wayland_surface_factory.cc: '--ozone-platform=wayland' is not compatible with Vulkan) and no window is ever created: a silent no-UI startup (the main process logs its [claude-cu] diagnostics: lines and stays alive, but nothing renders). Machines where Chromium never selects Vulkan (VMs, software GL) are unaffected and never hit this. Disabling the Vulkan feature is therefore a no-op on the unaffected machines and the fix on the affected ones - Chromium refuses Vulkan+Wayland outright, so no working render path is removed. Only the wayland arm is touched; X11 and XWayland (CLAUDE_USE_XWAYLAND=1) use --ozone-platform=x11 and keep Vulkan. Opt back in with CLAUDE_ENABLE_VULKAN=1.
• claude-desktop --diagnose now prints the assembled electron_args so future no-window reports show the active flags.
• README gained a "No window opens on Wayland" troubleshooting section and a CLAUDE_ENABLE_VULKAN env-var row. Launcher-only change; no patch or upstream-version bump.

Custom themes: theme the desktop-shell surfaces that ignore --bg-* (#149)

• add_feature_custom_themes.nim: the built-in element overrides now recolor the surfaces that don't read --bg-*, so the bundled catppuccin-* themes (and any custom theme) color the whole desktop shell out of the box instead of just the chat text. Three token layers paint independently of --bg-* and were staying their hardcoded neutral grey: the dframe-* frame classes (.dframe-sidebar -> --bg-200, .dframe-content/main -> --bg-100); the CDS/epitaxy surface tokens (--cds-surface-0…3, --cds-surface-popover/-panel, --surface-primary/-primary-elevated/-popover/-panel/-hud) that back the Settings dialog, popovers, cards, HUD and the Code tab; and the transcript scrims (.epitaxy-top-scrim/.epitaxy-bottom-scrim) that fade content under the titlebar with a fixed gradient. Each is now mapped onto the active theme's --bg-*, so they follow whatever theme is selected.
• Corrects the scope note from the 2026-06-21 entry. insertCSS() does reach the chat webview and its a.claude.ai/isolated-segment.html iframe - the unthemed surfaces were never a cross-origin-iframe block, they were these token layers bypassing --bg-*. themes/README.md is updated to describe the real layers and how to target them. The one thing genuinely out of reach is the OS window-control buttons (min/max/close), which the window manager draws as native decorations - themed from the desktop environment, not from here.

Links

• AUR Package
• Full Changelog