For Claude and Claude Code developers, this GitHub issue lands on a very practical pain point: the desktop app is still where a lot of the interesting workflow lives, but Linux users are left out. That matters not just for casual chatting, but for plugin testing, desktop extensions, computer use, dictation, and other parts of the Claude desktop experience that the CLI cannot replace.
What makes this request interesting is that it is not just “please support my favorite OS.” The author argues that Anthropic already ships Linux software, already runs Linux inside parts of the product, and already has a vibrant unofficial ecosystem filling the gap. That combination makes the absence of an official Linux desktop build feel less like a technical impossibility and more like a product decision that deserves a clear public answer.
.deb from an Anthropic-operated repository.aaddrick/claude-desktop-debian, is presented as a high-quality but unofficial workaround that repackages the Windows Electron build for Linux.What strikes me is that this is less a demand for “yet another app port” and more a request for product coherence. If Claude Desktop is the official place where extensions, computer use, and other advanced workflows live, then leaving Linux out creates a weird split: the CLI is first-class on Linux, but the GUI surface that developers need to test against is not.
I think the strongest part of the argument is the ecosystem angle. If people are building Claude Code plugins, then forcing them onto macOS or Windows just to test extension behavior is exactly the kind of friction that quietly kills developer adoption. That doesn’t sound dramatic, but in practice it can make a whole workflow feel half-supported.
What also stands out to me is the security angle. When a platform handles credentials and local system access, unofficial repackages are a pretty unsatisfying answer, even if the maintainers are competent. I’d be curious whether Anthropic sees this as a support burden, a security risk, or just a lower-priority platform choice — because those are very different reasons, and the issue is basically asking them to say which one it is.
I also think the Cowork discussion is strategically interesting, though maybe a little easy to overread. The fact that Linux is already part of the internal execution path does not automatically mean a polished Linux desktop app is trivial to ship. Still, it does weaken the “we don’t do Linux here” vibe. Perhaps that is why the author frames this as a call for a public position, not just a feature request.
If I were a Claude Code user on Linux, I’d want the official build for exactly the reasons laid out here: fewer hacks, less trust leakage, and a cleaner way to develop against the same desktop surfaces the product already exposes elsewhere. The web app and CLI are useful, but they are not the same thing.
The takeaway is simple: this is a credible, developer-centric request for Anthropic to close a real platform gap. Even if the answer is no, Linux users are asking for clarity — and if the answer is yes, it would remove a surprisingly large amount of friction.
Reference: [FEATURE] Official Claude Desktop build for Linux (Ubuntu LTS / Debian) · Issue #65697 · anthropics/claude-code](https://github.com/anthropics/claude-code/issues/65697)