Claude Desktop 5.11492.2 (patch release 2)
This release provides Claude Desktop version 5.11492.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.11492.2-2/claude-desktop-extra-5.11492.2-2-x86_64.pkg.tar.zst
# ARM64
sudo pacman -U https://github.com/patrickjaja/claude-desktop-extra/releases/download/v5.11492.2-2/claude-desktop-extra-5.11492.2-2-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.11492.2-2_amd64.deb
# ARM64
sudo apt install ./claude-desktop-extra_5.11492.2-2_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.11492.2-2.x86_64.rpm
# ARM64
sudo dnf install ./claude-desktop-extra-5.11492.2-2.aarch64.rpmNixOS / Nix
nix run github:patrickjaja/claude-desktop-extraAppImage (Any Distro)
# x86_64
chmod +x Claude_Desktop-5.11492.2-x86_64.AppImage
./Claude_Desktop-5.11492.2-x86_64.AppImage
# ARM64
chmod +x Claude_Desktop-5.11492.2-aarch64.AppImage
./Claude_Desktop-5.11492.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) | e3cb52614754376368dc79aff1f27d5e9449682386b821747ccd4008d7312520
|
| Arch pacman (aarch64) | 1c518be69def1a3e8599b1aa65df68f30863d05d121b8d9f228af2353a79b38f
|
| Tarball (x86_64) | ce64cd244a4e9a34cf082281308d5be30d4cbedbc65de472adf8a54728e08393
|
| Tarball (aarch64) | 90d7f5eff0ee8b22b4dcde30ba404bbfcec7dccad49826f16df4579418a0ec61
|
| AppImage (x86_64) | 1c47919c40577daf026f4f2f29b2db7ee3664d48aa6ba6100bbaa88c51e9cd25
|
| AppImage (aarch64) | b58beb4bb91b46c22776b49d99eccdb271495d87f2f2062e8f8b71f2b72a5234
|
| Debian (amd64) | 83f3f1d6688c17ec7c778e9dd1371ec0807d6c4f3e5d7290cfefdb05945c6de4
|
| Debian (arm64) | a7d3bbbb86e2a816de64bbdedf25edd3736aff708b191b02b40e02ed123c4142
|
| RPM (x86_64) | 45b7635accb35038b06a23a80645d3660eb0f99fa7508b1e9bde138d205eff17
|
| RPM (aarch64) | 13a2f4f1f014c847f018bc6e1accd9169d84fdad56803a9b309b307c535cff2a
|
Changes since last release
From CHANGELOG.md, 2026-11-13:
Upstream 5.11492.0
- Re-fitted for the re-minified build: allow non-Anthropic models, custom models, auto-archive grace, own-release update check and the Linux Computer Use patch. Nothing was absorbed upstream.
- Refusal-string baseline refreshed (reworded keychain connector error, which names the Linux keyring requirement).
Computer Use: read app controls (accessibility) - stable numbers, waiting, more actions
- Element numbers stay put. With the experimental accessibility switch on, a control keeps its
[N]across listings of its window for the whole task. Before acting, the control is checked to still be the one that was listed; a re-created control is found again only when that is unambiguous (same accessible id and name, or a unique role and name), otherwise the tool says so and sends nothing. - Results say whether anything was sent: refused before sending (safe to retry), or sent but not confirmed.
app_ax_findcan wait (at most 15 s) for a control to appear, go or change state, and can look inside one container, limit depth, list only containers (outline) or include plain text.- More actions:
app_clickcan bring a control into a state (checked, unchecked, expanded, collapsed, selected) and reports when it already was; newapp_focusandapp_scroll(scroll into view);app_typesets a slider's or spin button's value from a number. A bridge without these features keeps the four earlier tools. See Computer Use.
Jira issue tracker in the main window, opt-in (thanks @dels07, #333)
- New Community switch Jira issue tracker (Settings -> Extra -> Community Features -> Code, off by default). A Jira row in the sidebar, or Ctrl+Shift+J, opens a page over the content area: your Jira Cloud tickets (Assigned to me / Reported by me, a project filter, free JQL and named saved queries), a read-only detail panel (description, inline images and video with a zoomable viewer, attachments with Save to Downloads, the last five comments and a Details card), status changes from a menu, subtasks as expandable rows under their parent, Board / Backlog sections and moves from the project's Jira board, a Board view with drag-and-drop between the board's columns, and Send to agent, which starts a new Code session in a folder you pick (its own worktree in a git repository) with the ticket in the first message. Untrusted folders ask first in a native dialog.
- Needs your Jira Cloud site, Atlassian email and an API token (classic or scoped), stored encrypted with the system keyring per profile; requests go only to your site and
api.atlassian.com. Setup and limits: docs/jira-tracker.md (new patchadd_feature_jira_tracker). - Board view: the columns of the project's Jira board; drag a card to change its status (one fitting transition runs, several ask which, none or only ones that need fields send the card back with the reason). Board and Backlog moves read Jira's backlog again until the ticket shows in its new place.
- The page follows the claude.ai theme, custom themes included, while it is open. In light themes, secondary text is clamped to a readable lightness and opacity; dark themes keep their colours.
- Token scopes in Settings: an i beside the token field lists the scopes a scoped token needs, and Test connection names the token type and checks tickets, Board and Backlog, board columns and (Scrum) sprints, with the scopes each failed check probably lacks.
- Send to agent asks before every send: a native dialog shows the folder, the permission mode and the exact first message (ticket text is untrusted), Cancel is the default. Changing the Jira site clears the saved token so it is only ever sent to the site it was saved for; switching the tracker off or saving new credentials drops the cached board and attachment data; and a pending sidebar scan no longer brings the Jira row back after the switch is turned off.
- Known gaps: fixed 260 px board columns; the shared Extra settings styles of the Jira row can fall below AA contrast in light themes (separate fix); the native folder picker and trust dialog follow the system theme.