Tag: AI

Claude Desktop on Linux – update!

This post is an update to my earlier guide on installing Claude Desktop on Ubuntu/Debian. If you’re new here, start with that post first — this one covers what’s changed and how to update your existing install.

The Package is Back — and Better Than Ever

When we originally wrote the installation guide, the community-maintained claude-desktop-debian package by aaddrick was showing signs of going dormant. We’re happy to report that it has been fully resurrected and is more active than ever — sitting at 3,000+ GitHub stars, 75+ releases, and a thriving contributor community.

Even more importantly, the project now supports an APT repository, meaning Claude Desktop can update automatically alongside your other system packages. No more manually hunting for new .deb files.

There’s also a notable new feature: Cowork mode is now supported on Linux (experimental). You can run claude-desktop --doctor at any time to check your setup and see which isolation backend is active.

Step 1: Figure Out Which Method You Used

If you installed Claude Desktop a while back and don’t remember how you did it, run this:

apt-cache policy claude-desktop

Look at the output:

  • If you see a URL like https://aaddrick.github.io/claude-desktop-debian or https://pkg.claude-desktop-debian.dev — you already have the APT repo set up. Skip to Step 2.
  • If you see only 100 /var/lib/dpkg/status — you used the manual .deb method. Continue with Step 2 to add the repo.
  • If the command returns nothing — Claude Desktop isn’t registered with apt at all. Head back to the original guide for a fresh install.

Step 2: Migrate to the New APT Repository

Whether you’re coming from the manual .deb method or from the old APT repo URL, run the following to set up the current repository:

# Add the GPG key
curl -fsSL https://pkg.claude-desktop-debian.dev/KEY.gpg | sudo gpg --dearmor -o /usr/share/keyrings/claude-desktop.gpg

# Add the repository
echo "deb [signed-by=/usr/share/keyrings/claude-desktop.gpg arch=amd64,arm64] https://pkg.claude-desktop-debian.dev stable main" | sudo tee /etc/apt/sources.list.d/claude-desktop.list

# Update and install
sudo apt update
sudo apt install claude-desktop

If you already have Claude Desktop installed, the last command will upgrade it in place. Your MCP configuration at ~/.config/Claude/claude_desktop_config.json will be preserved.

From now on, Claude Desktop will update automatically whenever you run sudo apt update && sudo apt upgrade.

Troubleshooting

“The repository does not have a Release file”

If you had previously set up the old APT repo (hosted at aaddrick.github.io), you may see this error when running apt update. The repo moved to a new domain in April 2026. Clean up the old entry and add the new one:

sudo rm /etc/apt/sources.list.d/claude-desktop.list
sudo rm /usr/share/keyrings/claude-desktop.gpg

Then re-run the commands in Step 2 above.

If you want a one-liner instead (i.e., if you set up the old repo yourself and know what you’re doing), you can use sed to update the URL directly inside the existing file:

sudo sed -i 's|aaddrick.github.io/claude-desktop-debian|pkg.claude-desktop-debian.dev|g' /etc/apt/sources.list.d/claude-desktop.list

Quick explainer on that command: sed -i means “edit this file in place.” The s|old|new|g part means “substitute every occurrence of the old URL with the new one.” It’s a find-and-replace for the terminal.

Unrelated GPG errors from other packages

When running apt update, you may see GPG signature errors from completely unrelated packages — for my example, Spotify cropped up. These are separate issues that have nothing to do with Claude Desktop. A typical fix for Spotify looks like:

curl -sS https://download.spotify.com/debian/pubkey_6224F9941A8AA6D1.gpg | sudo gpg --dearmor --yes -o /etc/apt/trusted.gpg.d/spotify.gpg

For other packages, search for the package name + “GPG key ubuntu” to find the current key URL. The pattern is the same: download the key, convert it with gpg --dearmor, and drop it in /etc/apt/trusted.gpg.d/.

That’s it! If you run into anything not covered here, the GitHub Issues page for the project is active and well-monitored. And as always, claude-desktop --doctor is your first stop for diagnosing anything that seems off.

AI is a Mech Suit for Work — Use It

A massive shift in how we work is occurring, but are you trained in operating your new AI mech suit?

Now as those of you on my mailing list who don’t frequent Polish online casinos recently surmised, using AI to write a janky WordPress plugin is not a super-duper awesome idea. It can lead to security issues quickly!

Here’s a mech suit, in case you didn’t know what that meant:

Imagine if the Weyland-Yutani Corporation had forbid mech suits

Not just a mech suit for your work, but for your career.

Some companies are not allowing use of AI tools yet. If possible, leave such companies, or start learning and practicing on the side. As I mentioned in a recent post, when the AI bubble bursts and people realize AI is still around and not going anywhere, those companies and staff will need to scramble to upskill, or be left behind.

If it’s not possible to make a job change, make sure you are getting trained up in the AI skills that are top in your industry vertical.

Hat tip to Nate B. Jones for the metaphor. How have you found it helpful in your day-to-day? Drop me a message and let me know – I read every email!

How to Install Claude Desktop with MCP Desktop Commander on Ubuntu/Debian Linux

If you’re a Linux user who wants to run Claude Desktop with powerful Model Context Protocol (MCP) (https://modelcontextprotocol.io/) tools, this guide will walk you through the entire process. We’ll install Claude Desktop and set up the Desktop Commander MCP server, which allows Claude to interact with your desktop environment.

This Linux-beginner-friendly guide is based on my experience installing it this week on Pop!_OS on an Asus Nvidia machine, and was of course created with help from Claude. (June 2026 updated post is here!)

If you haven’t seen it in action, DesktopCommander MCP is a thing of beauty:

⚠️ Important Warnings and Prerequisites

Before you begin:

  • Backup any important data – always a good idea
  • System requirements: Ubuntu 20.04+ or Debian 11+/Debian-based distro (I’m running on Pop!_OS 22.04 LTS with Nvidia); Anthropic doesn’t publish RAM, disk space, or CPU requirements, but third-party online posts recommend 8GB ~ 32GB RAM
  • Terminal comfort: This guide involves using the terminal, but all commands are provided step-by-step

What You’ll Install

  • Claude Desktop: The desktop application for Claude AI
  • Node.js via NVM: JavaScript runtime needed for MCP servers
  • Desktop Commander MCP: Allows Claude to interact with your desktop (take screenshots, run commands, etc.)

Step 1: Update Your System

First, let’s make sure your system packages are up to date.

  1. Open your terminal by pressing Ctrl+Alt+T

  2. Update your package lists and upgrade existing packages:

sudo apt update && sudo apt upgrade -y

What this does: sudo gives you administrator privileges, apt (https://ubuntu.com/server/docs/package-management) is Ubuntu/Debian’s package manager, and this ensures your system has the latest security updates.

Step 2: Install Essential Dependencies

Install tools we’ll need for the installation process:

sudo apt install -y curl wget gnupg2 software-properties-common

What these tools do:

  • curl: Downloads files from the internet
  • wget: Alternative download tool
  • gnupg2: Handles cryptographic signatures for security
  • software-properties-common: Manages software repositories

Step 3: Install Node.js Using NVM

We need Node.js to run MCP servers. We’ll use NVM (Node Version Manager) which makes managing Node.js versions easier.

  1. Download and install NVM if you don’t already have it installed:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash
  1. Restart your terminal or reload your shell configuration:
source ~/.bashrc
  1. Verify NVM was installed:
nvm --version
  1. Install the latest LTS version of Node.js:
nvm install --lts
nvm use --lts
  1. Verify Node.js and npm are working:
node --version
npm --version

You should see version numbers after both commands.

Step 4: Download and Install Claude Desktop

Note: We’re using a community-maintained package since Anthropic doesn’t officially support Linux yet.

  1. Visit the Claude Desktop for Debian GitHub repository github.com/aaddrick/claude-desktop-debian in your web browser. (Unfortunately this package is deprecated, BUT there are a couple of active forks, so if you’re reading this in later months and the package is broken, check the active forks.) see my June 2026 UPDATE: the package has been resurrected!

  2. Go to the “Releases” section and download the latest .deb file (https://en.wikipedia.org/wiki/Deb_(file_format))

  3. Navigate to your Downloads folder in the terminal:

cd ~/Downloads
  1. Install the downloaded package (replace filename.deb with the actual filename):
sudo dpkg -i claude-desktop_*.deb
  1. If you encounter dependency issues, fix them with:
sudo apt install -f

What this does: dpkg is the low-level package installer for Debian/Ubuntu systems. The -f flag fixes broken dependencies.

Step 5: Create Claude Desktop Configuration Directory

Claude Desktop needs a configuration file to know about MCP servers.

  1. Create the configuration directory:
mkdir -p ~/.config/Claude

What this does: mkdir -p creates directories and any necessary parent directories. The ~ symbol represents your home directory (https://tldp.org/LDP/abs/html/special-chars.html).

Step 6: Test Desktop Commander MCP Server

Before configuring Claude Desktop, let’s make sure the Desktop Commander MCP server works.

  1. Test the MCP server directly:
npx @wonderwhy-er/desktop-commander@latest

You should see output like:

Loading schemas.ts
Loading server.ts
Setting up request handlers...
[desktop-commander] Initialized FilteredStdioServerTransport
  1. Press Ctrl+C to stop the test server.

What this does: npx runs Node.js packages without permanently installing them. This tests that the MCP server can start properly.

Step 7: Configure Claude Desktop for MCP

Now we’ll create the configuration file that tells Claude Desktop about our MCP server.

  1. Create the configuration file:
nano ~/.config/Claude/claude_desktop_config.json

What this does: opens nano a text editor for the terminal.

  1. Copy and paste this configuration into the file:
{
  "mcpServers": {
    "desktop-commander": {
      "command": "npx",
      "args": [
        "@wonderwhy-er/desktop-commander@latest"
      ]
    }
  }
}
  1. Save and exit nano:
    • Press Ctrl+X
    • Press Y to confirm saving
    • Press Enter to confirm the filename

Step 8: Launch Claude Desktop

  1. Start Claude Desktop from the graphical applications menu, or run from terminal:
claude-desktop

  1. Sign in with your Anthropic account when prompted

  2. Look for MCP indicators in the interface – you should see evidence that the Desktop Commander server is connected

Step 9: Test Your MCP Setup

  1. In Claude Desktop, try asking Claude to take a screenshot:

    “Can you take a screenshot of my current desktop?”

  2. Or ask Claude to check system information:

    “What’s my current working directory and what files are in my home folder?”

If Claude can respond to these requests with actual information about your system, congratulations! Your MCP setup is working.

Troubleshooting Common Issues

Issue: “Cannot find module” errors

Solution: This usually means there’s a problem with literal command substitution in your config file:

  1. Check your config file for any "$(which npx)" strings:
cat ~/.config/Claude/claude_desktop_config.json
  1. If you see "$(which npx)" anywhere, replace it with just "npx" – the simple form works when Node.js is properly installed via NVM

Issue: Claude Desktop won’t start

Solution: Check if all dependencies are installed:

sudo apt install -f
sudo apt update

Issue: MCP server not connecting

Solution: First, verify that Desktop Commander itself is working:

  1. Test the MCP server directly to confirm it’s functioning:
npx @wonderwhy-er/desktop-commander@latest

You should see output like:

Loading schemas.ts
Loading server.ts
Setting up request handlers...
[desktop-commander] Initialized FilteredStdioServerTransport
Loading configuration...
Configuration loaded successfully
Connecting server...
Server connected successfully

  1. If that works (press Ctrl+C to stop it), then the issue is with Claude Desktop’s configuration, not the MCP server itself

  2. Check Claude Desktop logs for connection errors – these are usually in the application’s output when started from terminal

Security Considerations

Important: The Desktop Commander MCP gives Claude SIGNIFICANT access to your system, including:

  • Taking screenshots
  • Running terminal commands
  • Accessing files

Best practices:

  • Only use this setup on personal machines, not shared computers
  • Review what you’re asking Claude to do before confirming actions
  • Consider creating a separate user account for testing MCP functionality
  • Keep your system updated with security patches

Keeping Everything Updated

Update Node.js

nvm install --lts
nvm use --lts

Update MCP packages

The @latest tag in our configuration automatically uses the newest version, but you can manually update:

npm update -g @wonderwhy-er/desktop-commander

Update Claude Desktop

Check the project forks on GitHub periodically for new .deb package releases and install them using the same dpkg process. (See my new post on how to update)

Uninstalling (If Needed)

Remove Claude Desktop

sudo apt remove claude-desktop

Remove Node.js and NVM

nvm uninstall node
rm -rf ~/.nvm

Remove the NVM lines from your ~/.bashrc file using a text editor.

Remove configuration files

rm -rf ~/.config/Claude

Next Steps

Now that you have Claude Desktop with MCP working, you can:

  1. Explore other MCP servers: Check the MCP ecosystem for additional tools
  2. Customize your setup: Add more MCP servers to your configuration
  3. Learn more about MCP: Read the official MCP documentation

Remember to always be cautious when giving AI systems access to your computer, and enjoy exploring the powerful combination of Claude AI with your Linux desktop.

Credits and Resources

  • Claude Desktop for Debian: Community package by aaddrick, deprecated at the time of this writing github.com/aaddrick/claude-desktop-debian
  • Desktop Commander MCP: Created by @wonderwhy-er – Thanks, Dmitry, for your help on Discord confirming that it was indeed the config file
  • Model Context Protocol: Developed by Anthropic (https://modelcontextprotocol.io/)

This guide was created based on real troubleshooting experience and community feedback. If you encounter issues, check the GitHub repositories for these projects or ask for help in Discord/Linux communities.

Repetitive emails? Have your AI craft replies

Do you have one or more types of emails that you need to reply to, but that you are sick and tired of handling? “If I have to answer the same question ONE more time I’ll snap” -type of emails?

Now let’s say you are not the administrator of your corporate or business email account for whatever reason. You want to implement some automations, and you have a vague idea that this should be something an AI can handle, but you’ve no access to the admin control panel needed to connect thing up.

There is a hack for that! This should absolutely NOT be used for sensitive communication, as you would basically be doing an end-run around any security controls your administrator has put into place.

But for nuisance emails an other non-sensitive emails, you can set up a Gmail account and an automatic script which can call an AI to generate replies to these emails, and then send the text back to you.

Details published here: https://claude.ai/public/artifacts/5c2560bd-b18b-43fb-b16e-3f1288dd1a36

Contact me to get this up and running, and get rid of those annoying email tasks!

Fun with Streamlit apps and LM Studio

Taking a fun course with Lonely Octopus, I’ve been learning how to use pandas to clean data for analysis, and also how to quickly build a proof of concept/MVP using Streamlit.

Installing Streamlit locally on Windows in Gitbash threw an error:

$ pip install streamlit

WARNING: Failed to write executable - trying to use .deleteme logic
ERROR: Could not install packages due to an OSError: [WinError 2] The system cannot find the file specified: 'C:\Python311\Scripts\watn311\Scripts\watchmedo.exe.deleteme'

“Watchmedo”? Sounded like malware. I got scared and shut off my wifi for a sec. Then I calmed down and decided to run it in a venv instead. Created the venv:

$ python -m venv myenv

Then activate it (I’m using Gitbash for my shell):

$ source myenv/Scripts/activate (or source myenv/bin/activate)

Then try again to install Streamlit and check if it installed properly:

$ pip install streamlit

$ streamlit --version
Streamlit, version 1.36.0

Now the moment of truth — run the little app:

$ streamlit run app.py

You can now view your Streamlit app in your browser.

Local URL: http://localhost:8501



It might also require installing OpenAI, so don’t forget to do that, too. BUT…

Running LM Studio is something I’m getting a lot more used to now. I’ve been playing with it and AnythingLLM for local document RAG chats.

So you don’t need to call OpenAI’s API — you can point your app at your local LM Studio server!

You have to grab the example code from inside LM Studio under “chat (python)”:

client = OpenAI(base_url="http://localhost:1234/v1", api_key="lm-studio")

Paste that into your Streamlit app.py file, replacing the ‘client’ variable. Make sure the model is loaded up, and that the server is running.

There are tons of settings to consider inside LM Studio. You also need to have enough memory to run the models! LM Studio’s Discord server is a good place to learn more.