Claude Desktop on Linux: the terminal is no longer mandatory

There’s a sentence that’s been quietly excluding people from this technology for a couple of years: “Desktop is macOS and Windows only — on Linux, you’ll use the terminal.”

Technically fine. Practically, it meant that on a Linux team, the designer, the analyst, the ops person, and the technical writer were all told the front door was a command line. Plenty of them concluded, reasonably, that this wasn’t for them.

That’s changed. The Claude desktop app now runs on Linux, in beta, and it’s the same app — not a cut-down version.

What you get

Ubuntu 22.04 or later, or Debian 12 or later, on x86_64 or arm64. Other Debian-based distributions that meet those requirements may work, but aren’t officially tested.

Inside, it’s the full thing: Chat, Cowork, and Code tabs, parallel sessions, visual diff review, an integrated terminal and editor, and live app preview. Everything a macOS or Windows user has, with the exceptions listed further down.

The most consequential part of that list is Cowork — the mode built for non-technical work, where you hand Claude a folder of real files and it does multi-step work on them. That’s the surface that makes Claude useful to people who don’t write code, and until now Linux users simply didn’t have it.

Installing it

This is the one honest caveat: installation is a terminal job. Not because the app requires the command line, but because that’s how software is installed on Debian-based Linux. You do it once.

The recommended route is Anthropic’s apt repository, because it means updates arrive with your normal system updates rather than needing to be chased.

Add the repository — you may need curl and gnupg first on a fresh install:

sudo apt install curl gnupg
sudo curl -fsSLo /usr/share/keyrings/claude-desktop-archive-keyring.asc https://downloads.claude.ai/claude-desktop/key.asc

Before going further, verify the key is Anthropic’s:

gpg --show-keys /usr/share/keyrings/claude-desktop-archive-keyring.asc

The fingerprint should read 31DDDE24DDFAB679F42D7BD2BAA929FF1A7ECACE. If gpg reports the file can’t be opened or holds no valid OpenPGP data, the download failed — check that your network can reach downloads.claude.ai and try again. Skipping this check isn’t a formality; verifying a signing key before trusting a repository is the whole point of the mechanism.

Register the repository and install:

echo "deb [arch=amd64,arm64 signed-by=/usr/share/keyrings/claude-desktop-archive-keyring.asc] https://downloads.claude.ai/claude-desktop/apt/stable stable main" | sudo tee /etc/apt/sources.list.d/claude-desktop.list
sudo apt update && sudo apt install claude-desktop

Then launch Claude from your application launcher — or run claude-desktop — and sign in.

If your environment can’t reach the apt repository, you can download the .deb directly from the repository’s package pool and install it with sudo apt install ./claude-desktop_*.deb. Be aware that a package installed this way doesn’t receive updates; registering the repository is what keeps it current.

Signing in

The Linux app authenticates exactly like macOS and Windows: a claude.ai subscription, or your organisation’s SSO.

One thing to know: Desktop doesn’t accept a Claude Console API key. If API-key authentication is what you need, that’s the CLI’s territory — same engine, different door. Enterprise deployments routing Desktop through Google Cloud’s Agent Platform or an LLM gateway have their own configuration path.

Keeping it updated

The app doesn’t update itself on Linux. Updates arrive with your system’s regular package updates:

sudo apt update && sudo apt upgrade

Your distribution’s graphical software updater will also pick them up, so in practice most people never think about it again after install.

To remove it: sudo apt remove claude-desktop. That also removes the signing key, so delete the repository entry too — sudo rm /etc/apt/sources.list.d/claude-desktop.list.

What isn’t in the beta yet

Beta means beta, and the gaps are specific:

• Computer Use — app and screen control isn’t available on Linux.
• Dictation — voice input isn’t in the Linux app. The CLI has voice dictation if you need it.
• Quick Entry global hotkey — works on X11; on native Wayland it needs your desktop environment’s GlobalShortcuts portal.
• Fedora and RHEL — only Debian-based distributions are supported today, with more said to be coming.

None of those touch the core loop. Chat, Cowork, and Code all work, which covers essentially all of what most people do.

If you’re on an unsupported distribution, the CLI runs the same Claude Code engine and supports a much wider range of Linux systems. It’s not a downgrade in capability — it’s the Power Track route, which was the only route until now.

Why this matters more than a release note

On this site we’ve always treated the terminal as an optional Power Track rather than the front door, with one honest exception: Linux users didn’t get a choice. Desktop wasn’t available to them, so the command line was mandatory rather than opt-in.

That exception has mostly closed, and the consequence is organisational rather than technical. On a Linux-based team, the people who most needed the non-technical surface — operations, finance, HR, marketing, anyone whose work is files rather than code — can now be given the same app as everyone else. The conversation shifts from “Linux users will need to learn a terminal first” to “install this and open a folder.”

If you’re setting up for the first time, the getting-started guide applies directly once the app is installed — everything past the install step is identical across all three platforms. And if you’re still weighing the app against the CLI, that comparison is here.