Official Claude Desktop Linux support — Cowork, Dispatch, and remote session integration

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Claude Desktop — including Cowork, Dispatch, and computer use — is currently
macOS-only. This excludes Linux users from the full Claude Desktop experience
at a time when these agentic features are most compelling.

This is particularly acute for researchers, academics, and clinical scientists,
who overwhelmingly use Linux as their primary workstation OS. As a pathologist
and researcher at Karolinska University Hospital working on molecular tumor
profiling, bioinformatics pipelines, and translational cancer research, my
entire computing environment runs on Linux — as does that of most of my
colleagues across pathology, bioinformatics, and oncology.

Linux is not a niche choice in scientific computing: it is the default, from
hospital research servers to university HPC clusters. The active community
workarounds (claude-desktop-debian, Snap Store packages) demonstrate that
demand is real, motivated, and currently unmet by official channels.

Proposed Solution

An official Linux build of Claude Desktop with full Cowork, Dispatch, and
remote session integration, on par with the current macOS experience.

A phased approach would be entirely acceptable:

Phase 1 (near-term): Official Linux build covering Cowork, remote sessions,
and Dispatch — features that are already platform-agnostic and functional
via Claude Code CLI on Linux.

Phase 2 (later): Computer use / GUI automation on Linux, developed with
community input on supporting the range of desktop environments (GNOME, KDE,
Wayland, X11, etc.).

Claude Desktop appears to be built on Electron, which has native Linux support,
suggesting Phase 1 is achievable without a disproportionate engineering effort.

Alternative Solutions

• Continue using Claude Code CLI on Linux (already works well, but lacks

Cowork, Dispatch, and the integrated Desktop UI experience).

• Use unofficial community builds (claude-desktop-debian, Snap), which are

unsupported, lag behind releases, and cannot guarantee security or feature parity.

• Access Claude via browser (loses agentic desktop integration entirely).

None of these alternatives are satisfactory for professional, production use
in research or clinical environments.

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

A concrete and immediate use case: iterative, agentic knowledge work in
academic research on Linux.

As a researcher supervising PhD students and leading multiple translational
projects, I would use Cowork on Linux for:

• Grant applications: drafting, restructuring, and refining across multiple

iterative cycles, with Claude accessing local reference documents, prior
applications, and project files.

• Research programs and PhD project plans: tailoring background, aims, and

methodology documents to each student's project, iterating on structure
and scientific narrative with full file context.

• Data analysis strategy and code: designing and executing R-based analysis

pipelines for molecular pathology and tumor microenvironment data — from
initial exploratory analysis through to manuscript-ready figures — with
Claude able to read, run, and iterate on scripts directly in the working
environment.

All of this currently happens on Linux. Cowork would transform these workflows
from assisted writing into genuinely agentic collaboration — but only if it
runs on the OS where the work actually lives.

Additional Context

• Anthropic's own infrastructure and the open-source ecosystem underpinning

Claude's capabilities run on Linux. Official Linux support would be a
meaningful reciprocity toward that community.

• The Cowork/computer use launch (March 2026) being macOS-only made this gap

newly acute for Linux users.

• Related closed issue: #38276 — closed as out of scope for the Claude Code

repo, but the underlying need is unresolved and shared by many users.

• I would be glad to participate in testing on academic Linux environments

(Ubuntu/Debian, HPC-adjacent setups) if that would help move this forward.