Claude for Linux: Desktop App or CLI, Which One?
See wetin Claude support for Linux today: beta apt desktop app, Claude Code CLI, editor plugins, and the paid plans wey cover each one.
Which parts of Claude dey run natively for Linux today
Claude for Linux dey run for four separate surfaces, and as of October 2026 all four dey work for ordinary Ubuntu or Debian machine. The desktop app installs from Anthropic's apt repository and e dey beta. Claude Code CLI (command line interface) na compiled binary, and e dey run for more distributions than the desktop app. The web app for claude.ai only need browser, while the API na HTTPS endpoint wey you call from your own code.
Three features wey macOS and Windows get dey missing or limited for the Linux desktop beta: Computer Use, wey Claude dey use control apps for your screen; voice dictation; and the Quick Entry global hotkey. Anthropic document say Computer Use and dictation no dey available for Linux. The Quick Entry hotkey dey work for X11 session, but for native Wayland session e need your desktop environment's GlobalShortcuts portal. So, if that portal no dey, the hotkey no dey available. echo $XDG_SESSION_TYPE prints x11 or wayland and tells you which case you dey. The CLI get its own voice dictation, so the dictation gap dey inside the desktop app, no be for Claude itself.
Availability dey change, so make you treat this page as description of the surfaces and check the current state before you plan around am. The last section list the pages wey you need check.
Install Claude desktop app for Ubuntu or Debian
The documented requirements na Ubuntu 22.04 or later, or Debian 12 or later, for x86_64 (wey dpkg dey call amd64) or arm64. Other Debian-based distributions fit work, but dem never test am. Fedora and RHEL never get package yet, so for those ones you go use CLI or browser.
Install am from apt repository instead of downloaded .deb file. The Linux app no get updater of its own, so new versions go reach you only through your package manager. Registering the repository na wetin make apt upgrade see dem.
sudo apt install curl gnupg
sudo curl -fsSLo /usr/share/keyrings/claude-desktop-archive-keyring.asc \
https://downloads.claude.ai/claude-desktop/key.asc
gpg --show-keys /usr/share/keyrings/claude-desktop-archive-keyring.ascgpg --show-keys suppose print fingerprint 31DDDE24DDFAB679F42D7BD2BAA929FF1A7ECACE. Compare am before you register the repository, because signing key wey you no check na key wey you dey trust blindly. If gpg report say the file no hold valid OpenPGP data, the download fail, and apt update go fail later with NO_PUBKEY BAA929FF1A7ECACE.
Registering the repository na one deb line wey you write to /etc/apt/sources.list.d/claude-desktop.list. Copy that line from Anthropic's Linux install page, code.claude.com/docs/en/desktop-linux, exactly as dem print am there. The repository address na the part of this procedure wey fit change most likely, and line wey person type from memory na wetin go leave you dey look at E: Unable to locate package claude-desktop afterwards. Read the line before you paste am: arch=amd64,arm64 na why apt for any other architecture no find anything, and signed-by= point to the keyring file wey you just check. This one limit that key to this repository only, instead of trusting am for everything else apt dey read.
sudo apt update && sudo apt install claude-desktopStart am from your application launcher, or run claude-desktop for terminal. Sign in with your claude.ai account, or through your organisation's SSO (single sign-on) if your company set am up. Those na the two sign-in options wey Anthropic's Linux install page list, and e send API key users go CLI. Anthropic document another deployment mode for the same app separately: when you configure am with an inference provider (Amazon Bedrock, Google Cloud's Agent Platform, Microsoft Foundry, an LLM gateway, or the Anthropic API directly), the sign-in screen go offer to skip Anthropic authentication. The provider go handle inference and billing for Chat, Cowork, and Code. Those docs name one Linux location for the managed configuration, /etc/claude-desktop/managed-settings.json, and the Linux install page now link to the third-party deployment docs. For devices wey no get Claude Desktop configuration, Claude Desktop 3.1623.1 or later also offer Use your Claude API account for the standard sign-in screen. There, you fit sign in with Claude Console or enter API key without advance configuration. For Claude Desktop 4.23118.0 or later, that link dey hidden for computer login where organisation block other accounts, even when device management no dey.
Cowork tasks wey run for your own machine use virtual machine, so hardware virtualization must dey turned on and your user must dey inside kvm group (sudo usermod -aG kvm $USER, then log out and log back in). No be every Cowork task dey run locally. Since October 6, 2026, new Cowork tasks for Pro, Max, and Ultra plans dey run for Anthropic's cloud, with no setting to keep dem for your computer. Team and Enterprise organisations wey turn on the unified Chat and Cowork experience also run tasks for cloud. For those plans, the virtual machine matter only for tasks wey already start for your computer. Anthropic dey direct new work wey must stay local to Claude Code inside the desktop app.
E: Unable to locate package claude-desktop mean say apt never read the repository. cat /etc/apt/sources.list.d/claude-desktop.list suppose show the deb line wey you write, and dpkg --print-architecture suppose print amd64 or arm64, because dem never publish packages for other architectures. Updates go then arrive with the rest of your system, from sudo apt update && sudo apt upgrade.
Wetin browser alone fit do
claude.ai dey work for any current browser for any distribution. Na why e dey work for Fedora, RHEL, Arch, openSUSE and anything else wey no get package. Browser also get Claude Code on the web. For there, the session dey run for cloud infrastructure instead of your machine. By default, na Anthropic infrastructure. But e fit use your organisation own self-hosted environment if your organisation route sessions go there. E always use your subscription credentials.
The important limit na to understand wetin browser fit do. Browser by itself no fit read files for your own server or run command for there. Anything wey need access to your machine require software for that machine. This means CLI, desktop app, or configured self-hosted runner. Cowork cloud sessions fit reach connected local folders through desktop app while the app dey open.
Wetin CLI dey give you wey web app no dey give
Start claude inside one directory, and e go work for that directory. Na this be the main difference, and everything else follow from am.
- E dey read and edit files for your working directory, and e dey ask before e apply edits for Manual mode. Auto mode dey apply edits with background safety checks, and na the built-in default for current interactive sessions unless settings or policy change am. Start with
claude --permission-mode defaultif you wan review actions by yourself. - E dey run shell commands under the session permission mode, so e fit build project, run test suite, read log, or inspect service for the machine itself.
- E dey run without interactive session:
claude -p "read the nginx error log and summarise it"dey print one answer and exit, and na this you use from cron job or pipeline. For Claude Code 2.1.302 or later, these runs dey start for Manual mode when no permission mode dey set, and dem dey deny actions wey need approval unless you provide approval mechanism; pass--permission-mode automake classifier review dem. You decide how the answer go look, because output style dey edit the system prompt behind every reply and e fit keep scripted run short while interactive session explain itself. - E dey connect MCP (model context protocol) servers with
claude mcp add, and this one dey give model tools beyond filesystem. - E dey run where graphical desktop no dey at all, and na so every VPS (virtual private server) wey you go ever rent be.
Na this last point make server guide dey care about CLI. Rented server get SSH (secure shell) and nothing else, so terminal na the only surface wey fit dey there with you. Running am this way get its own rules, and running Claude Code on a VPS inside tmux explain everything for there, while using Claude for everyday sysadmin work cover the jobs wey worth giving am.
Editor integrations dey between the two. VS Code extension need VS Code 1.94.0 or later, and e dey give you graphical panel inside the editor, with diffs and plan review. E bundle private copy of CLI for that panel and e no put claude for your PATH, so if you type claude for integrated terminal, you still need standalone install. Editors wey build on VS Code dey install the same extension from Open VSX registry, and JetBrains plugin dey available too.
You need Node.js to run Claude Code for Linux?
No, not with the recommended install. Native installer dey download compiled binary, and that binary no dey run on Node.js.
curl -fsSL https://claude.ai/install.sh | bash
claude --versionclaude --version suppose print version number like 2.1.211 (Claude Code). If something no look correct, run claude doctor. E dey print read-only diagnostics about the install and your settings files without starting session.
Node.js only matter for npm route. As of October 2026, npm package dey ask for Node.js 22 or later. For older Node.js, npm dey print EBADENGINE warning instead of failing, because package dey pull the same native binary as per-platform dependency and link am into place.
npm install -g @anthropic-ai/claude-codeFor npm 12, postinstall step dey skipped by default, so claude no fit run. If npm --version start with 12, use native installer above or add Claude Code to allow-scripts for your user npm configuration before you reinstall.
No run that with sudo. Documentation warn against sudo npm install -g because e leave root-owned files for your global npm prefix. This make the next unprivileged install or update fail because of permissions. When npm global directory no writable, background auto-update stop working, and claude doctor list the fixes.
Anthropic still dey publish signed package repositories for Debian, Fedora, RHEL and Alpine. So sudo apt install claude-code dey work almost like desktop package, with im own signing key for https://downloads.claude.ai/keys/claude-code.asc.
You suppose install am for each user or system-wide?
The native installer na per-user install. E dey put launcher for ~/.local/bin/claude as symlink wey point to ~/.local/share/claude/versions/, e no need root, and e dey update itself for background. Each user for the machine get separate copy with separate version.
Package manager install na system-wide. One binary dey serve every user, e need root, and e no dey auto-update through Claude Code. You upgrade am with sudo apt update && sudo apt upgrade claude-code, na the same command wey you already dey run for everything else for the machine.
Choose per-user install for machine wey you dey log into as yourself, and this cover most VPS work. Choose package install for shared server or machine image, where you want one version for everybody and you want updates to follow your own schedule. For native install, two settings for ~/.claude/settings.json decide how updates go behave:
{
"autoUpdatesChannel": "stable",
"env": {
"DISABLE_AUTOUPDATER": "1"
}
}The stable channel dey follow release wey about one week old and e dey skip releases wey get major regressions. DISABLE_AUTOUPDATER only stop the background check, so claude update still dey work and you still control when new version go land. This matter for server where long job dey run unattended and you prefer make the binary no change underneath am.
Log in through SSH, and make the session stay alive
Two Linux-specific problems dey show the first time you run the CLI for rented server. The login process need browser, but server no get browser. If SSH connection drop, e go carry the work wey dey run along with am.
tmux dey solve the second problem. tmux session belong to the tmux server for the remote machine, not to your connection. So if link drop, process still dey run.
tmux new -s claude
claudeDetach with Ctrl-b then d, and come back later with tmux attach -t claude.
The login na the first problem. Run claude and copy the separate authorisation URL wey show above the terminal paste prompt. Open that URL for browser on your own computer. After you sign in through that URL, browser go show login code instead of returning to localhost. Paste that code into terminal for the Paste code here if prompted prompt, and terminal go report Login successful.
For session wey need start when nobody dey watch am, claude setup-token go open the same browser authorisation and print one year OAuth token for terminal. E no save the token anywhere, so copy am and set am where you need am.
export CLAUDE_CODE_OAUTH_TOKEN=your-tokenThat token need paid plan and e fit only make model requests. Treat am like password wey get one year lifespan. Where to keep am, and how to stop agent from reading am back, na the subject of keeping secrets away from AI agents.
Small servers get one more problem. Installation need roughly 512 MB free memory, and the documented hardware requirement to run am na 4 GB RAM or more. So for 1 GB instance wey get small free memory, kernel out-of-memory killer fit end the installation, and installer go then report:
Setting up Claude Code...
Installation was killed before it could finish (exit code 137). This usually means the system ran out of memory.Add swap, then run installer again. Swap na disk space wey kernel dey use as overflow memory. E slow well-well pass RAM, but e enough to finish installation.
sudo fallocate -l 2G /swapfile
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfileswapon enable the file for this boot only. Add one line for /swapfile to /etc/fstab if you want am back after reboot. The subject of wetin else to lock down before you allow agent run commands for live server na running Claude Code safely on a VPS.
Where your Claude credentials dey live for Linux
For Linux, /login dey write the credential go ~/.claude/.credentials.json with file mode 0600. macOS normally dey put the same credential for encrypted Keychain, but e go fall back to the same plain file when Keychain reject the write. For Linux, the token na plain file inside your home directory, and every process wey dey run as your user fit read am. If you set CLAUDE_CONFIG_DIR, e go move the file under that directory.
Two things follow from this. Backup of /home contain active login, so if you copy that backup go shared machine, anybody else wey fit read am don get access to your account. And machine image wey you build from box where you don log in go ship that login to every instance wey you clone from am. Run /logout before you take any snapshot.
Credential precedence dey catch people wey get subscription and API key at the same time. When ANTHROPIC_API_KEY dey set for your shell, Claude Code go use am once you approve am, so your subscription go remain unused while the key dey charge per token. /status go show which credential dey active, and unset ANTHROPIC_API_KEY go return you to the subscription login.
Logins dey expire. Within three days before expiry, the startup line go read Your login expires in 3 days, and that warning no dey block request. After expiry, if the login no fit refresh, every model request go fail with Login expired · Please run /login. Know this before you leave unattended session running through weekend, because that kind session go stop making progress and no fit recover by itself.
One Claude subscription cover everything?
One paid plan cover every place with the same login, except for some Enterprise plans. Pro, Max, Ultra or Team account go sign you in to claude.ai for browser, desktop app, CLI and VS Code extension. Na the same subscription each time. New or self-serve Enterprise plan outside HIPAA-ready organisations dey work like this too, and the single Enterprise seat includes Claude Code. Older Enterprise plans still get different seat types. For those plans, Claude Code surfaces need Chat + Claude Code seat, or Premium seat for older seat-based plan. Chat-only or Standard seat no include dem. HIPAA-ready Enterprise organisations still use separate Chat and Chat + Claude Code seat types. For HIPAA-ready Enterprise plan, Claude Code need Chat + Claude Code seat. BAA coverage for terminal and Code tab of Claude Desktop need HIPAA configuration or applicable zero data retention coverage. HIPAA configuration no cover VS Code and JetBrains extensions or cloud sessions. For Pro, Max, Ultra, Team and seat-based Enterprise plans, na one usage allowance across all the surfaces. So, long CLI run for your server go reduce wetin desktop app get left. When any surface start reject work, you need know which limit window you don reach and wetin you fit do.
Usage-based Enterprise plan no get included allowance wey fit finish. Every surface bill at API rates from the first token. Free claude.ai plan no include Claude Code access. Without paid plan, CLI fit sign in with Claude Console account. Or, if your organisation dey use Amazon Bedrock, Google Cloud's Agent Platform or Microsoft Foundry, you fit authenticate through that provider without browser login. With claude.ai subscription or SSO sign-in, Claude Code parts for desktop app need paid plan. The separately configured third-party mode wey we describe above, and the Claude API account option for unmanaged devices where e dey available, let desktop app use Console or provider billing instead.
API na different product with different billing. Console account bill per token based on wetin you actually send. This one better for service wey you dey build, instead of typing for terminal. Setting ANTHROPIC_API_KEY move CLI go that billing path. Na choice you make; e no be fallback. For standard mode, desktop app sign in with OAuth. For third-party mode, e use the credential for its own configuration.
Prices and plan limits dey change too often to repeat here. Two pages dey track the current numbers: wetin Claude Code really cost and which Claude plan you need. If you dey compare per-token billing with monthly plan, API compared with subscription explain where the break-even point dey.
Errors wey you go actually see during install
bash: claude: command not found immediately after install finish successfully. The binary dey for ~/.local/bin/claude, but that directory no dey inside your shell search path. Confirm am with echo $PATH | tr ':' '\n' | grep -Fx "$HOME/.local/bin"; e no go print anything when the entry no dey. Fix am for bash with echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc, then run source ~/.bashrc. Installing the VS Code extension by itself no ever create that file, because the extension dey keep its CLI copy inside the extension directory.
Error loading shared library libstdc++.so.6. Either the installer download the wrong binary variant, usually the musl build for a glibc system, or you dey use a musl system wey no get the runtime libraries. The wrong variant fit happen when musl cross-compilation packages dey installed and detection read dem wrongly. Run ldd --version 2>&1 | head -1: output naming GNU libc or GLIBC mean say you dey on glibc and you receive the wrong binary, so remove the install and run the installer again. For Alpine and other musl systems, the fix na the opposite, apk add libgcc libstdc++ ripgrep.
Two copies of claude for one box. which -a claude go list every match inside your PATH. A native install na symlink from ~/.local/bin/claude go ~/.local/share/claude/versions/, legacy local npm install dey under ~/.claude/local/, and npm -g ls @anthropic-ai/claude-code go show global npm install. Remove the ones wey you no want, because na stale copy earlier inside your PATH dey make fixed bug look like say e never fix.
Wey to check the current state
- Linux desktop status, requirements and install commands: code.claude.com/docs/en/desktop-linux
- Supported distributions and every install method for the CLI: code.claude.com/docs/en/setup
- Which platforms get an app to download at all: claude.com/download
- Which plan get wetin, and how much e cost: claude.com/pricing
Dem check the Claude API account sign-in policy, unattended permission defaults, SSH login flow and credential storage on November 7, 2026. Other version numbers and dates for this guide still remain snapshots from October 2026. The main structure na wetin still dey valid: four surfaces, one login across the paid ones, and one decision about whether the CLI belong to your user or the whole machine.
FAQ
Claude desktop app dey for Linux?
Yes. As of October 2026, e dey beta, and e support Ubuntu 22.04 or later plus Debian 12 or later for amd64 or arm64. Install am with sudo apt install claude-desktop after you add Anthropic's apt repository and signing key, so new versions go arrive with your normal system upgrades. The Linux build get the same tabs as the macOS app, including the Claude Code tab. Computer Use and voice dictation never dey for the Linux build yet, and the Quick Entry global hotkey dey work for X11 but e need your desktop environment's GlobalShortcuts portal for native Wayland session. Fedora and RHEL no get package, so for those distributions use the CLI or claude.ai for browser.
I need Node.js to run Claude Code for Linux?
No be for the recommended install. curl -fsSL https://claude.ai/install.sh | bash downloads compiled binary wey no use Node.js at runtime. Node.js only matter if you install the npm package, wey ask for Node.js 22 or later as of October 2026. For older Node.js, npm prints EBADENGINE warning and the install still finish, because the same native binary dey come in as per-platform dependency. Never install am with sudo npm install -g, because e leave root-owned files inside your npm prefix and break later updates.
How I go log in to Claude Code over SSH?
Run claude and copy the separate authorisation URL wey show above the terminal's paste prompt. Open that URL for browser on your own computer, no be for the server. After you sign in through that URL, the browser go show login code instead of returning to localhost. Paste that code for the Paste code here if prompted prompt. For sessions wey go start when nobody dey there, run claude setup-token and set the printed token as CLAUDE_CODE_OAUTH_TOKEN wherever e dey needed.
Where Claude Code dey store my login for Linux?
For ~/.claude/.credentials.json with file mode 0600, or under CLAUDE_CONFIG_DIR when you set that variable. Linux no use keychain; macOS normally use the encrypted Keychain but e fall back to the same plain file when the Keychain reject a write. Any process wey dey run as your user fit read the Linux credential file. Therefore, /home backup or machine image carry working login: run /logout before you take snapshot or copy system. If ANTHROPIC_API_KEY dey also set for your environment, e take priority over the stored subscription login once you approve am, and /status show which one dey active.
My Claude Pro subscription cover the CLI and the web app?
Yes. Pro, Max, Ultra or Team plan sign you in to claude.ai, the desktop app, the CLI and the VS Code extension with one account. Enterprise dey do the same, except say older and HIPAA-ready Enterprise plans include Claude Code only for seats wey carry am, such as Chat + Claude Code seats. HIPAA-ready organisations use separate Chat and Chat + Claude Code seat types, and na only Chat + Claude Code seats include Claude Code. The free claude.ai plan no include Claude Code, so the terminal CLI need paid plan, Claude Console account, or cloud provider wey your organisation use, such as Amazon Bedrock, Google Cloud's Agent Platform or Microsoft Foundry. The desktop app support subscription or SSO sign-in and configured third-party inference. For devices wey no get Claude Desktop configuration, version 3.1623.1 or later also offer Claude API account option wey accept Console sign-in or API key without advance configuration. For version 4.23118.0 or later, that link hide for computer login where organisation block other accounts, even when device management no dey. The API dey billed separately per token from Console account, and Console account na different product from subscription.