Most Claude Desktop distributions target Windows; this project fills the gap for Linux users by repackaging the official Windows application into native Linux packages and distribution formats so Claude can run without Wine or full virtualization. It focuses on system integration and updateability rather than forking the client—so you get the upstream UI with Linux-friendly packaging and optional sandboxing.
What Sets It Apart
- Native packaging across ecosystems: produces .deb/.rpm packages, AppImages, an AUR package and a Nix flake so the same build output works on Debian/Ubuntu, Fedora/RHEL, Arch, and NixOS — this simplifies deployment and automatic updates via distro package managers. This means easier installs and system upgrades compared with ad-hoc AppImage-only distributions.
- MCP (Model Context Protocol) support: includes MCP integration with a well-known config location (~/.config/Claude/claude_desktop_config.json), making it straightforward to connect to local or proxied MCP servers for advanced workflows. Useful for users who rely on MCP-enabled tooling or custom servers.
- Linux-oriented integration and optional sandboxing: provides system tray, global hotkey (Ctrl+Alt+Space), and experimental Cowork mode with a bubblewrap-based isolation backend (plus a host fallback). The project exposes which isolation backend will be used via a built-in
--doctordiagnostic, so you can assess sandboxing and dependency status before running. - Upstream-preserving approach and trade-offs: this is an unofficial repackage that keeps the upstream Claude Desktop binary and UI, minimizing behavior changes but inheriting upstream limits (and Anthropic’s consumer terms). The repo also includes packaging fixes, CI, and various distro-specific workarounds contributed by the community.
Who It's For — and When to Look Elsewhere
Great fit if you run Debian/Ubuntu (or other Linux distros) and want the official Claude Desktop experience as a native package with automatic updates, MCP support, and desktop integration without managing a VM or Wine. Choose this when you prefer distro package management and easy integration with your desktop environment.
Look elsewhere if you need an officially supported Anthropic Linux client (this is unofficial), require a fully functional KVM-based cowork VM on Linux (KVM backend is present but non-functional on Linux builds), or if you must avoid any packaging that bundles upstream proprietary binaries. Also be mindful of security trade-offs: the host backend provides no isolation, and the bubblewrap backend mounts your home directory read-only except for the working directory.
