Is there an official Claude Desktop build for Linux?

As of October 2026, Anthropic has not released an official Linux build of Claude Desktop. The supported clients on Linux are the web interface at claude.ai and Claude Code in the terminal.

Can I use unofficial Claude Desktop packages for Linux?

Unofficial wrappers exist but are not supported by Anthropic and carry security risks. They may not be maintained, can break when Anthropic makes changes, and could intercept your conversations. Stick to official clients.

How do I install Claude Code on Bazzite's immutable file system?

Use a Distrobox container for a clean install, or install Node.js via Homebrew to user space. Both approaches survive base image updates. Avoid installing tools directly to the base layer with dnf, as those changes are not preserved.

Can Claude Code load MCP servers on Bazzite?

Yes. Claude Code supports MCP servers through its config file, the same way Claude Desktop does on macOS and Windows. Configure your servers in Claude Code's settings and they work within any Claude Code session.

Does the Claude web interface support MCP on Bazzite?

The web interface supports connectors you have authorized in your Claude account settings, but it does not load local MCP servers from your machine. For local MCP tool access on Bazzite, use Claude Code.

Claude Desktop on Bazzite: Access and Setup Options

Bazzite is an immutable Linux distribution built on Fedora. Claude Desktop does not ship a native Linux package, but several supported access routes work on Bazzite. Here is how to identify the right one and avoid unofficial wrappers.

October 19, 2026Updated October 21, 20265 min read

Bazzite is an immutable, gaming-focused Linux distribution based on Fedora Atomic. As of October 2026, Claude Desktop does not publish an official Linux package, so there is no supported way to install Claude Desktop directly on Bazzite or any other Linux distribution. The options for Claude on Bazzite are the web interface, Claude Code in the terminal, and MCP servers you connect to supported clients. fenbs preserves project context across whichever client you use, so the work is not tied to any single app.

Before looking for workarounds, confirm what you actually need. If you need Claude for conversation and writing, the web interface at claude.ai works on any browser. If you need MCP tool access, Claude Code is the supported terminal client.

What Claude Desktop is and why it matters

Claude Desktop is the official desktop application from Anthropic for macOS and Windows. Its main advantage over the web interface is MCP support: Claude Desktop can load MCP servers from a local config file, giving Claude access to local tools, file systems, and external services. That MCP capability is what most people looking for "Claude Desktop on Linux" actually want.

Understanding that the MCP capability is the goal, not the app itself, points you toward the right alternatives on Bazzite.

Option 1: Claude Code in the terminal

Claude Code is Anthropic's official terminal-based AI coding assistant. It runs on Linux, including Bazzite, and supports MCP servers through its own config. If MCP tool access is your goal, Claude Code is the supported route on Linux.

Install Claude Code via npm (Node.js must be installed first). On Bazzite, use rpm-ostree to layer Node.js, or install it via Homebrew in a user-space installation, which avoids the immutable file system constraint. Then install Claude Code globally with npm install -g @anthropic-ai/claude-code.

Once installed, configure your MCP servers in the Claude Code settings file and they work the same way as in Claude Desktop. See what Claude Code is for an overview of its capabilities and the Claude Desktop app overview for a comparison with Claude Desktop.

Option 2: the Claude web interface

claude.ai runs in any modern browser and works on Bazzite without any installation. It supports connectors you have authorized through your Claude account settings. If your use of Claude is primarily conversation, document review, or working with cloud-based connectors rather than local MCP tools, the web interface is a full solution.

The limitation is that the web interface does not load local MCP servers. If you need Claude to access local tools, files, or services on your Bazzite machine, Claude Code is the right client.

Avoiding unofficial Linux wrappers

Search results for "Claude Desktop Linux" often surface unofficial wrappers: Electron apps, Flatpak packages, or community-built AppImages that claim to package Claude Desktop for Linux. These are not from Anthropic, are not supported, and may not be kept up to date with Claude's changes.

The risk with unofficial wrappers is that you do not know what code is running around Claude's interface. An unofficial wrapper can intercept your conversations, inject content, or fail silently when Anthropic makes API changes. Stick to official clients: the web interface, Claude Code, or other supported clients listed at Integrations.

Installing Claude Code on Bazzite

Bazzite's immutable base layer means you cannot install packages with dnf in the traditional sense; they do not persist across updates unless you use rpm-ostree layer or install to user space. The recommended approach for development tools on Bazzite is to use a Distrobox container or install to user space with Homebrew or similar.

Distrobox: create an Ubuntu or Fedora container with distrobox create, enter it, and install Node.js and Claude Code inside the container. MCP servers run inside the container and Claude Code reaches them normally.
Homebrew: install Homebrew to ~/.linuxbrew, then install Node.js via Homebrew. This keeps everything in user space and survives base image updates.
rpm-ostree layer: for a system-wide Node.js install, use rpm-ostree install nodejs. This is applied on the next reboot and persists.

How fenbs helps

Keep project context available across clients

If you switch between the web interface and Claude Code depending on the task, fenbs keeps the project context available to both. Connect whichever client you are using over MCP, and both read the same decisions, tasks, and Where we left off. The work is not tied to which client you opened.

Create a free account

Free for one person · No credit card · Works with Claude, ChatGPT, Cursor and more

Managing Node.js versions on Bazzite

Claude Code requires Node.js 20 or later. If you install Node.js via rpm-ostree, confirm the version available in the Fedora repository matches the requirement before layering. If you use Homebrew or a Distrobox container, you can install any Node.js version you choose without affecting the base system.

A version manager like nvm or Volta works well inside a Distrobox container and in Homebrew-managed user-space installs, giving you the flexibility to switch Node.js versions per project if needed. This is particularly useful on Bazzite where keeping the base layer minimal is a design goal.

How to do this with fenbs

Create a free account at fenbs. Add the projects you work on regularly.
Install Claude Code on Bazzite using a Distrobox container or Homebrew for Node.js.
Connect Claude Code to fenbs over MCP from Integrations. This gives Claude Code access to your project context, decisions, and tasks.
Write the standing rules for your projects as Decisions and rules so every Claude session, whether via Claude Code or the web, starts from the agreed setup.
Save progress in fenbs before switching clients or ending a session. The next session starts from Where we left off.

fenbs works with any supported MCP client. Whether you use Claude Code on Bazzite or claude.ai in the browser, the project context is the same. For the list of supported clients, see Integrations.