I tested the new Claude Desktop on Linux – here’s how it compares to rival apps


claudedesktophero

Jack Wallen/ZDNET

Follow ZDNET: Add us as a preferred source on Google.


ZDNET’s key takeaways

  • Claude Code finally has a Linux desktop app.
  • The app works swimmingly if you play by the rules.
  • Trying to make it work locally was an exercise in futility.

As a hard-core Linux user, I’m always on the lookout for apps that enable Linux to keep pace with competing platforms. You might be surprised that, even in this age of AI, competitive open-source options are not hard to find. For example, I’ve been using both Alpaca and Moose for some time without issue. Both of these apps serve as GUIs for instances of locally installed Ollama (which is how I typically like to roll with AI). They offer well-designed GUIs, the flexibility to work locally or in the cloud, and efficient use of system resources.

But sometimes, I yearn to work with a more mainstream option.

Such is the case with the newly released Claude Code Linux desktop app, which offers all the features found in the MacOS and Windows versions, and even lets you enable developer options to expand the feature set.

Also: I quit ChatGPT for a free, private, and local AI called Ollama – here’s why

Before I get into this, it’s important to understand that when I use AI, I almost always use it locally. I’ve installed Ollama on most of my machines I have. Why? I’m not straining the power grid or compromising my privacy. I will always choose local AI over cloud-based.

That said, I still wanted to kick the tires of the Claude Code Linux desktop app to see how it compared to the competition. 

Here are the important bits for me:

  • The app has to have a well-designed GUI that makes interacting with models simple.
  • The app needs to easily connect to locally installed AI (such as Ollama).
  • The app needs to function exactly as it does on other operating systems.
  • The app needs to use system resources wisely.

Does the Claude Code Linux desktop app live up to that checklist? Let’s find out.

Installing Claude Code on Linux

First things first: Install Claude Code on Linux. With many GUI AI apps, I can open the app store of my distribution, search for the app (such as Alpaca or Moose), and install. With Claude Code, I had to add the necessary repository before installation. One thing to keep in mind: Currently, Claude Code desktop is only available for Debian and Ubuntu-based distributions. 

Also: How to install and configure Claude Code, step by step

Here are the commands required:

Add Anthropic’s signing key: sudo curl -fsSLo /usr/share/keyrings/claude-desktop-archive-keyring.asc https://downloads.claude.ai/claude-desktop/key.asc

Add the repository: 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

Update and install: sudo apt update && sudo apt install claude-desktop

With the installation complete, I opened the Claude Code app from my desktop menu and was greeted — you guessed it — by a well-designed GUI.

Claude Code

The Claude Code Linux desktop app has a well-designed GUI.

Screenshot by Jack Wallen/ZDNET

It’s time to dive in.

Connecting to locally installed AI

This is where things got a bit bumpy (which wasn’t that surprising). I’ve set up plenty of local AI for various desktop clients, but (sadly) Claude Code was not the easiest. In fact, it was rather complicated, and I wouldn’t have been able to make it work without also installing Claude Code from within Ollama itself (with the ollama launch claude command, which allowed me to select an LLM to download and use with Claude Code).

I downloaded the Qwen6 LLM, which is 15 GB, so be careful what you wish for. Until you pull a model, the GUI won’t be able to find one.

Also: Want local vibe coding? This AI stack might replace Claude Code and Codex – for free

With that taken care of, I had to enable Developer options in Claude Code (Help > Troubleshooting > Enable Developer Options. After a relaunch, I could then go to Developer > Configure third-party inference. This is where things should have made it possible to connect to my locally installed AI. The settings look like this:

Claude Code

This should work as expected. Unfortunately…

Screenshot by Jack Wallen/ZDNET

Once you’ve done that, click Apply changes. You’ll then need to select a model for use. Scroll down to the Models section and click Add model. This is where I ran into what looked like an insurmountable hurdle. Even though I instructed Claude Code to use a local gateway base URL, it refused to see any of the models I’d pulled, and no matter how I tried to configure it, the Claude Code desktop app refused to comply. 

What this means is that I’m stuck with using a free Anthropic plan, which is pretty limited (especially when you try to get Claude Code to write an app for you). In the end, you cannot reliably use the Claude Code desktop app with local AI. Bummer.

Does the app function as on other operating systems?

This is where we get some good news. I tested the Linux app against the MacOS app, and they are identical. Feature for feature, you won’t find any difference (other than slight UI changes) between the two. 

Also: 5 reasons why I still prefer Perplexity over every other AI chatbot

Huzzah.

Does the app use system resources wisely?

This would have been a much more revealing test had the Claude Code desktop app functioned with locally installed AI. As is, it relied mostly on cloud-based resources, so using the desktop app didn’t put even the slightest dent in my machine.

Here’s the query I used for my testing:

Write a Linux GUI app for Pop!_OS COSMIC Desktop for creating invoices for clients. It needs to be able to keep track of clients and different deliverables (such as articles and videos), include custom fields, and export invoices to PDF documents.

Even though my free account couldn’t finish the query, while it worked, my machine continued performing fine. When I tested that against a locally installed AI desktop app that would function with local AI, the query brought my machine to a temporary halt while it ground away at the task.

Also: I’ve tested so many desktop AI tools, but Hermes with Ollama is my new favorite – here’s why

In the end, I was disappointed that I was unable to connect the Claude Code desktop app to my locally installed AI, but I can still say this: If you have an Anthropic account and are looking for a tool to simplify using Claude Code on your Linux desktop, this is definitely the way to go. I’ve launched Claude Code through Ollama (which does work quite well), but going that route is not for the faint of heart. 

If you want simplicity, this new Claude Code desktop app for Linux is a good option. Just make sure your Anthropic account is paid for and ready to go. If you want to use local AI on Linux, however, I’d suggest sticking to Alpaca or Moose.





Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


I reluctantly upgraded from my Pixel 4a in late 2024, which means I spent four years clinging to a phone that still felt like a phone. Part of that was the size. The Pixel 4a was small enough to use without performing thumb yoga, a disappearing luxury now that flagships have settled into pocket-tablet territory. That’s an argument for another day.

The uglier issue is what happened after I moved on. In January 2025, Google pushed an automatic Android 13 update to Pixel 4a phones. Google’s own support page says the update reduced available battery capacity and affected charging performance on some impacted devices. Reddit users were less polite. One r/Pixel4a post said the battery suddenly had “around 40% of its former capacity” after the patch.

For poor ol’ 4a, that was basically the death knell.

When an update becomes the problem

A dying battery is normal. A four-year-old phone needing service isn’t exactly a scandal. Batteries age, screens fail, ports loosen, and gravity remains undefeated.

This felt different. The phone didn’t simply get old in someone’s pocket. Its usable life changed after a company-controlled patch, and the owner was left to deal with the result. The Verge reported that the update was tied to overheating-risk mitigation and reduced charging capacity by more than 50% on affected units. Battery safety is real. It still doesn’t erase the experience of waking up to a phone that suddenly can’t survive the day.

That’s what update death looks like. Software doesn’t just support aging hardware anymore. It can also decide when that hardware becomes miserable to keep using.

When every patch feels haunted

My wife, who’s rocking an S24 Ultra, has a different version of the same dread. She keeps running into Reddit threads about Samsung Galaxy phones and the dreaded green line, that bright vertical scar that makes a screen look like it has been reassigned to a cyberpunk prop department. One r/S23 user wrote that a green line appeared on a carefully maintained phone after about a year and a half, then said Samsung service quoted a screen replacement because the warranty was over. Another Samsung Community post claimed a green-line issue appeared after an August update, with the display allegedly working perfectly before it.

Reddit isn’t a forensic lab with avatars. A green line can come from boring hardware failure, not corporate villainy with a release calendar. Still, the anxiety is real. People don’t only worry that an update will move a button or ruin a camera setting. They worry it might be the thing that nudges a working device from “old” to “not worth repairing.”

Modern gadgets are never fully handed over. They keep phoning home. They keep asking for patches. They keep depending on decisions made long after the receipt has faded. Ownership now comes with a quiet asterisk.

The graveyard got software updates

Planned obsolescence used to sound like tinfoil-hat consumer paranoia, which was convenient for everyone selling the new thing. Then regulators started writing it down in boring official language. In 2018, Italy’s competition authority fined Samsung and Apple after finding that software and firmware updates caused serious malfunctions, reduced performance, and sped up replacement of older phones. Samsung was fined €5 million, while Apple was fined €10 million.

Apple’s battery-throttling mess made the suspicion harder to laugh off. In the US, Apple agreed to a settlement of up to $500 million over claims that it slowed older iPhones, while a separate multistate settlement required Apple to pay $113 million over alleged misrepresentations around iPhone batteries and performance throttling. Consumers weren’t hallucinating the pattern. The receipts were scattered across court filings, regulatory decisions, and phones that suddenly felt older than they had the day before.

Europe seems less willing to accept “trust us” as a product-lifetime policy. New EU rules for smartphones and tablets started applying on June 20, 2025, covering durability, repairability, battery life, and software updates. New labels put some of that lifespan math in front of shoppers before checkout.

The post-warranty graveyard used to be easy to recognize: cracked screens, swollen batteries, and charging ports full of pocket lint. Now the graveyard has paperwork, compatibility warnings, and software that slowly stops cooperating. The gadget can still turn on. It can still look fine on a desk. Then one day the company changes what “usable” means, and the thing you paid for starts practicing being trash.



Source link