Claude Desktop 5.1231.2 (patch release 3)
This release provides Claude Desktop version 5.1231.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-extraArch Linux (manual package)
# x86_64
sudo pacman -U https://github.com/patrickjaja/claude-desktop-extra/releases/download/v5.1231.2-3/claude-desktop-extra-5.1231.2-3-x86_64.pkg.tar.zst
# ARM64
sudo pacman -U https://github.com/patrickjaja/claude-desktop-extra/releases/download/v5.1231.2-3/claude-desktop-extra-5.1231.2-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_5.1231.2-3_amd64.deb
# ARM64
sudo apt install ./claude-desktop-extra_5.1231.2-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-5.1231.2-3.x86_64.rpm
# ARM64
sudo dnf install ./claude-desktop-extra-5.1231.2-3.aarch64.rpmNixOS / Nix
nix run github:patrickjaja/claude-desktop-extraAppImage (Any Distro)
# x86_64
chmod +x Claude_Desktop-5.1231.2-x86_64.AppImage
./Claude_Desktop-5.1231.2-x86_64.AppImage
# ARM64
chmod +x Claude_Desktop-5.1231.2-aarch64.AppImage
./Claude_Desktop-5.1231.2-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) | 1a84f2501d57a8b216dff5c0f1db8fdf7965867e9d6662529f9440fc5969b548
|
| Arch pacman (aarch64) | e92d74e6673aaca06269d9011a06d342b73f733e56a56312deaca378bbe48811
|
| Tarball (x86_64) | e84d7a9b7471b03569c57c98d24de141c4df6987da50ff667a54ed32c08471b4
|
| Tarball (aarch64) | 3da023951f3d5299b53de5bc0f49023645c1cb4fd5ade329e564a691395670d3
|
| AppImage (x86_64) | 97ac7b139b2557286989fbae7e0d82c71e94e29a03c3145270e884fb2559caf4
|
| AppImage (aarch64) | 34e97704ced1045a671553a0892502b8d257508d48412438db393386c266b4ce
|
| Debian (amd64) | 99a251fb6568f138defae92c060f87bad78b1831d6ed50f0d4261c13d5b7d213
|
| Debian (arm64) | f1b2ffb742783810eff35e2af8bb226bfe12bbf0ea850a6e5bbe91a0e3993ce2
|
| RPM (x86_64) | 48e4066527ef3377138ee5bd996db21ff48f931d864e4dce849dd32fb2c735b1
|
| RPM (aarch64) | 8602b2f17bcea5ee238ff8a8ce035f04b578b34d001fd9a2e25c967eb0f99f3b
|
Changes since last release
From CHANGELOG.md, 2026-11-11:
Computer Use: no screen-share dialog after a failed capture, Stop sharing on Ubuntu, the dock of a maximized window, X11 title bars
- sway, Hyprland, niri, river and GNOME Wayland: a screenshot whose bridge capture fails tells Claude it failed and that taking it again once is reasonable; a second failure in a row in the same turn tells it to stop and tell you (naming
claude-patches.logandCOWORK_SCREENSHOT_CMD), and a GNOME portal session that could not start is reported with its own advice. It no longer falls back to Electron's own capture, which on Wayland raised the desktop's screen-share picker (GNOME's "share your screen" dialog) and blocked the tool call until someone answered it. On GNOME a screen-cast frame that does not arrive in time is waited for once more first. X11 keeps that silent fallback, andCOWORK_SCREENSHOT_CMDstill overrides. A capture still running when the turn ends is stopped with it, on X11 too (no image after the turn). - Stop sharing is noticed at once on Ubuntu. Its GNOME session runs with umask 0002, so the bridge's folder in
$XDG_RUNTIME_DIRwas group-writable and was not watched; the stop was noticed only at the next action. Inside your own private runtime folder the app now sets it to 0700 and watches it. A folder another account could write to is still not watched. - Docking a maximized Claude window: when the window manager applies the un-maximize only after the dock (GNOME Wayland, about 1 in 14 turns) and the window comes back large over the app Claude works in, the dock size is asked for once more, by the window manager's own late resize when it comes; a dock that still does not hold is logged as a
[claude-cu] dock:line. - X11 with a reparenting window manager (xfwm4 and others): a click on an approved app's title bar, its buttons or its border is allowed like a click in the window; it was refused as landing on a bare window number. The bundled
x11-bridgeresolves a frame point to the window's app, also for window managers that nest the client deeper; the invisible shadow margin of client-side-decorated windows no longer counts as the window, and it looks through windows that do not take clicks (Claude's "Claude is using your computer" glow), so panels, docks and the desktop behind the glow are judged as themselves. A window that names no app is still refused, now with the explicit "no grant can cover it" message. Claude's own title bar is still recognised as Claude's. See Computer Use.
Upstream 5.1231.2
- Re-fitted to the new release (Electron 45.2.1, Claude Code 2.1.321; fitted against 5.1231.0, released as 5.1231.2, which passes unchanged): the Computer Use enable gates and glow setter, the renderer recovery pair (upstream's reason filter now returns a verdict; the SIGKILL fallback sits in upstream's shared kill helper, so it also ends a stalled renderer behind the "reload limit reached" error card, and after our kill upstream reloads at once), the updater idle state (now carries a "held on low data" variant), the Quick Entry command-line toggle (the shortcut registration gained a screen-locked callback, which is passed through) and the tier-pin check of the non-Anthropic models switch.
- Computer Use follows the new
computerUseEnabledpolicy key: a managedcomputerUseEnabled: falseturns Computer Use off on Linux as it does on upstream's platforms; unset ortrueleaves it available. - The drawn cursor in the Computer Use glow works on X11. When upstream turns it on (server flag
1916550538), the glow on X11 with a compositing manager becomes a thin rim and an arrow glides to each target before the real pointer follows and a press ring plays, as with upstream's own Linux X11 backend. The real pointer stays visible. With the flag off, and on every other session, the glow and all input are unchanged. To try it now, switch on Drawn cursor in the glow on Settings -> Extra -> Cowork (Linux) and restart. - Non-Anthropic gateway models: upstream's
/v1/modelsdiscovery now filters through the gateway validator the switch already guards, so the separate discovery guard is gone. The build fails if discovery stops going through that validator. - Trusted Auto-fix PR authors: upstream now also requires the signed-in
ghaccount to have push access to the repository before Auto-fix arms; this applies to PRs from listed authors too (they reportno_pushotherwise). - Settings -> Extra -> Deployment lists the new managed keys (213):
computerUseEnabled,remoteFileDownloads,organizationAnnouncement,allowStandardUserUpdates(macOS only), and, locked, three more reserved Docs/Slides/Designs keys and the browser-extension policy keys (ExtensionSettings,NativeMessagingAllowlist,NativeMessagingBlocklist,NativeMessagingUserLevelHosts).entraScopeis retired upstream and removed. - The GrowthBook flag catalogue in
claude-desktop-extra.jsonccovers 5.1231.0 (854 flags: 79 new, 2 removed). - New upstream, behind server flags and without a platform restriction: Chrome Web Store extensions in the built-in browser, with Linux native-messaging host folders (
/etc/claude-desktop/native-messaging-hosts, Chrome's own). Upstream keeps them off while the app runs with--no-sandbox, which AppImage launches andCLAUDE_DISABLE_SANDBOX=1do.
The GitHub connector binary is shipped where the app runs it (5.1231.x)
- Upstream 5.1231 ships
github-mcp-serverinresources/app.asar.unpacked/and starts it from there. The repack now keeps every file upstream ships unpacked, with its file mode, and the build fails if one is lost.
Computer Use in cloud sessions on GNOME Wayland, niri and river, screenshots inside action batches (#326)
- Cloud Cowork, Dispatch and chats linked to this computer work on desktops that cannot tell which window is in front or under the pointer (GNOME Wayland, and niri and river where the compositor gives no window positions). Clicks were refused as landing "on the desktop shell" and typing as "no app is frontmost". These sessions now follow the whole-screen rules Anthropic's own Wayland code uses: once at least one app is approved, clicks and keystrokes go to whatever is on screen, except Claude's own windows: a click aimed at one is discarded by Anthropic's own input guard, which the Linux backends arm around every input they send on GNOME Wayland, niri, river and the fallback Wayland paths (where that guard does not exist, an X11 session without the bundled x11-bridge, the click is refused). A read-only approval still blocks input, nothing is allowed before an app is approved, typing is refused while Claude's own window has keyboard focus, and input is refused while one of Claude's dialogs is open.
list_granted_applicationslists "Entire screen" there. X11, sway, Hyprland and KDE Plasma Wayland keep the per-app check, and on niri and river input is still refused while an unapproved app is in front. - A screenshot taken inside a batch of actions reports its monitor and size, so with two or more monitors it is no longer rejected as taken on monitor "display undefined", and the click after it no longer fails with "coordinate could not be scaled" (every backend except KDE). A screenshot without a chosen monitor uses the default monitor, on GNOME the shared one.
- What Claude is told about access on GNOME says the session cannot tell which window is in front or under a point.
claude-patches.loggets one[claude-cu] no window info: <backend> (<reason>)line per task when a backend answers without window info. See Computer Use.
Computer Use screenshots on X11 show the approved apps under the glow (#327)
- Cloud Cowork, Dispatch and chats linked to this computer: masked screenshots on X11 no longer come back as one solid colour while the "Claude is using your computer" glow is up. The bundled
x11-bridgelooks through Claude's own glow and teach overlay (new--ignore-window, honoured only for Claude's own click-through overlay windows), so the approved apps show with the glow's rim over them as on screen; other apps stay masked. - On X11 without a compositing manager (i3, openbox, xfwm4 with its compositor off) the glow is no longer shown: Electron drew it as an opaque black screen there.
x11-bridge doctorreportscapabilities.compositing; the glow stays off while it is false or unknown, a compositor stopped between tasks is noticed when the next task starts (a glow already shown is closed at once), andclaude-patches.logsays so once. Teach mode on X11 still needs a compositing manager. See Computer Use. - Builds fail when the bundled
x11-bridgelacks thesedoctorcapabilities (scripts/check-bridge-contract.sh, run by local builds and CI).
Computer Use in Code sessions and local Cowork takes the Computer Use lock
- On X11, sway, Hyprland, niri and GNOME Wayland, Code sessions and local Cowork tasks take Anthropic's Computer Use lock like every other session type: at the first Computer Use action of a turn, released when the turn ends, also on Stop and errors. Not taken by the access tools (
request_access,list_granted_applications,list_apps),wait,switch_display, a batch of onlywait/switch_display, and the app-scoped accessibility tools. A call that arrives after its turn ended (for example from a background subagent) is answered " aborted (user interrupt)." and takes nothing. KDE Plasma Wayland already worked this way. - While Claude works in those sessions the Claude window un-maximizes, docks at the top right and stays above other windows, and takes focus back at the end of the turn (tiling window managers may ignore the move); the "Claude is using your computer" glow shows (X11 with a compositing manager). Escape (Anthropic's X11 grab, or with Escape stops Computer Use on the watcher) and Stop sharing stop the session's running turn the way Stop does: the session's Claude Code process is restarted with the next message. The "screenshots are not filtered" note of Ask before Computer Use controls an app now comes once per turn. On GNOME Wayland the screen-sharing session starts and ends with each turn.
- One session at a time: while another session holds the lock, a Code session or local Cowork task is told "Another Claude session is currently using the computer" and its action does not run; before, it could drive the desktop while a cloud session held the lock. A cloud Cowork or Dispatch task releases the lock when the Claude app sees its turn end; where the app does not (for example a task whose page is not open in the app), Anthropic's idle sweep releases it after 12 minutes without Computer Use.
- X11: the Claude window stays clickable while Claude works (Stop in the docked panel), and Claude's own clicks on it are refused instead; after the turn the whole restored window takes clicks again on xfwm4 (before, clicks outside the docked size went to the window behind it). Claude's own Escape reaches the app while Anthropic's Escape grab is registered (the switch off). The first screenshot of a turn waits for the dock, so Claude's own window no longer covers the app in it (also cloud sessions). A batch of actions stops when the turn is stopped, as Anthropic's does. See Computer Use and Escape stops Computer Use.
- In those sessions the glow and the teach overlay follow the monitor Claude works on (each screenshot on another monitor and each
switch_displaymove them, as in cloud sessions), Anthropic's drawn arrow glides to a click target before the click instead of jumping, the check of the first click target waits for the dock, and a turn that ended with the mouse button held no longer makes the next turn's arrow jump.
Computer Use screenshots on Hyprland, web-app approvals, --diagnose without KWallet (#329, #330)
- Hyprland: masked screenshots (cloud Cowork, Dispatch, and Code sessions with "Ask before Computer Use controls an app" on) capture each approved window on its own, so a notification, launcher or other layer-shell surface neither hides an approved window nor shows in the image; before, a full-output overlay such as Omarchy's notification host could leave one solid grey image. A window another window sits over is shown whole, with a note naming what is in front. Needs the new wlroots-bridge; sway and other compositors keep the output capture.
- When no approved window can be shown (another workspace, minimized, not open, or covered on sway and X11), Claude gets a text with the reason per approved app instead of a grey image; an image that shows some apps can carry a short note about covered or missing apps. See Computer Use.
- On Wayland sessions a web app installed as its own desktop entry (a Chromium-family
--app=<url>window) is an app of its own: approving it covers only its window, and a browser approval does not include it. On X11 and XWayland its window counts as the browser. A terminal app started from a desktop entry shows up under its terminal, and the text tells Claude which app to request access to. claude-desktop --diagnoseno longer starts KWallet on desktops that do not use it (#330), and shows each bridge's screenshot filter (how screenshots are filtered and what the filter cannot cover).- The build fails when the bundled wlroots-bridge predates the per-window mask report (
scripts/check-bridge-contract.sh --wlroots-caps).
Release pipeline: package installs when the runner cannot resolve Ubuntu's mirrors
- Release jobs that install packages check the runner's resolver first; when it cannot resolve Ubuntu's package mirrors, the job uses public DNS resolvers for its remaining steps (
scripts/ci-dns-fallback.sh). Nothing changes while the runner's own resolver answers.
Computer Use: the glow and Anthropic's drawn cursor on sway, Hyprland and niri, kept out of screenshots
- sway, Hyprland and niri: the "Claude is using your computer" glow shows while Claude uses the computer, as on X11 and KDE Plasma, drawn by the bundled
wlroots-bridgein a click-through overlay on the monitor Claude works on. With Anthropic's drawn cursor on (server flag1916550538) it becomes the thin rim and Claude's arrow, which glides to each target before the click exactly as on X11 and rings on each press; the real pointer stays visible. Also with Claude on XWayland. GNOME Wayland has no glow yet; KDE Plasma keeps the glow its own bridge draws, without the drawn cursor. - Settings -> Extra -> Cowork (Linux) -> Computer Use has two new rows: Show the glow while Claude uses the computer (on by default; off removes the glow, the rim and the drawn cursor on X11 and on the sessions above from the next task, Computer Use itself works the same; KDE Plasma keeps its bridge's glow), and Drawn cursor in the glow for flag
1916550538, marked as an Anthropic flag: it follows Anthropic unless you force it on or off, and it is the same override as on the Anthropic page. On both pages a switch now shows the saved override and the status line says when it only applies after a restart; before, a page you came back to showed the running value, so a click could save the same value again. - The screenshots Claude receives no longer contain the drawn cursor, its press ring or the glow's badge (X11 and the overlay above): they are hidden for the instant of each capture, so the arrow no longer covers the spot Claude just clicked. The rim or glow stays up and may show at the screen edges.
- sway, Hyprland and niri: screenshots work on a monitor plugged in while the app runs; they failed with "zoom region does not intersect the captured output" until a restart.
CDB_CU_DEBUG=1adds[claude-cu] wl-glow: trace:lines with a timestamp per overlay command and per real pointer command, and[claude-cu] glow trace:lines for the X11 capture hide. See Computer Use and Environment variables.