{"id":433,"date":"2026-07-08T05:32:12","date_gmt":"2026-07-08T05:32:12","guid":{"rendered":"https:\/\/abrarqasim.com\/blog\/how-to-uninstall-claude-code\/"},"modified":"2026-07-08T05:32:12","modified_gmt":"2026-07-08T05:32:12","slug":"how-to-uninstall-claude-code","status":"publish","type":"post","link":"https:\/\/abrarqasim.com\/blog\/how-to-uninstall-claude-code\/","title":{"rendered":"How to Uninstall Claude Code: The Clean Removal I Actually Run"},"content":{"rendered":"\n

Last updated: July 2026. Reflects the native-installer era (Claude Code 2.1.x) and the npm path Anthropic now treats as legacy.<\/em><\/p>\n\n\n\n

\n

TL;DR<\/h3>\n\n\n\n

First figure out how you installed Claude Code, because the uninstall command depends on it. Native installer: rm -f ~\/.local\/bin\/claude && rm -rf ~\/.local\/share\/claude<\/code>. Homebrew: brew uninstall --cask claude-code<\/code>. WinGet: winget uninstall Anthropic.ClaudeCode<\/code>. npm: npm uninstall -g @anthropic-ai\/claude-code<\/code>. None of those touch your config. To wipe settings, MCP servers, auth tokens and session history, also delete ~\/.claude<\/code>, ~\/.claude.json<\/code>, and any project-local .claude\/<\/code> and .mcp.json<\/code>. If claude<\/code> still runs after all that, you have a second install or an old shell alias.<\/p>\n<\/div><\/div>\n\n\n\n

Why the uninstall is harder than it should be<\/h2>\n\n\n\n

Claude Code is not one thing you delete. It is a binary, a config directory, a JSON file at your home root, a per-project .claude<\/code> folder, an MCP file, maybe a VS Code extension, maybe a JetBrains plugin, and maybe the Claude Desktop app, all writing into the same ~\/.claude<\/code>. The docs describe a clean removal in ninety seconds. My reality was that I ran npm uninstall -g @anthropic-ai\/claude-code<\/code>, typed claude<\/code>, and the CLI still launched. A shell alias from an old install script. Twenty minutes I did not budget.<\/p>\n\n\n\n

The other trap is the January 2026 migration. Anthropic moved from npm to a standalone native installer around v2.1.15. If you first installed Claude Code before that, you probably ran npm install -g<\/code>. If you followed the “migrate” instructions, you now have the native binary at ~\/.local\/bin\/claude<\/code> and the old npm shim somewhere in your PATH<\/code>. Uninstalling one and leaving the other is the single most common way people end up with a “how is this still running?” problem.<\/p>\n\n\n\n

This post is the checklist I run on my own machines. Nothing here is a trick. It is just the boring surface area you have to sweep.<\/p>\n\n\n\n

Step 1: figure out how you installed it<\/h2>\n\n\n\n

Before you delete anything, ask the shell where it thinks claude<\/code> lives. On macOS, Linux, or WSL:<\/p>\n\n\n\n

which claude\n# common answers:\n# \/Users\/you\/.local\/bin\/claude          -> native installer\n# \/opt\/homebrew\/bin\/claude              -> Homebrew (Apple silicon)\n# \/usr\/local\/bin\/claude                 -> Homebrew (Intel) or apt\/dnf\n# \/Users\/you\/.nvm\/versions\/node\/...\/bin\/claude   -> npm global\n# \/usr\/local\/bin\/claude (symlink)       -> npm via system Node<\/pre>\n\n\n\n
On Windows PowerShell:<\/p>\n\n\n\n
where.exe claude<\/pre>\n\n\n\n
If you see more than one path, that is your answer for why the last uninstall attempt did not stick. Handle each install separately, in the sections below.<\/p>\n\n\n\n
You can also ask Claude Code itself. Run claude doctor<\/code>. It tells you the install method it detected, the version, the update channel, and whether the config directory is writable. That output is the fastest way to figure out what you are actually dealing with, and I run it before I touch anything.<\/p>\n\n\n\n
Native installer: the one Anthropic recommends<\/h2>\n\n\n\n
If you installed with curl -fsSL https:\/\/claude.ai\/install.sh | bash<\/code>, or the equivalent PowerShell one-liner, you have the native binary. It lives at ~\/.local\/bin\/claude<\/code> with the version files under ~\/.local\/share\/claude<\/code>. There is no package manager tracking it, so you delete both by hand.<\/p>\n\n\n\n
macOS, Linux, WSL:<\/p>\n\n\n\n
rm -f ~\/.local\/bin\/claude\nrm -rf ~\/.local\/share\/claude<\/pre>\n\n\n\n
Windows PowerShell:<\/p>\n\n\n\n
Remove-Item -Path \"$env:USERPROFILE\\.local\\bin\\claude.exe\" -Force\nRemove-Item -Path \"$env:USERPROFILE\\.local\\share\\claude\" -Recurse -Force<\/pre>\n\n\n\n
Older versions of the native installer shipped a claude uninstall<\/code> subcommand. If you can still run claude --version<\/code>, try it first. On a current build it just calls the same rm commands, but on older builds it also handled a few edge cases around PATH shims that the manual delete does not. Both paths get you to the same end state.<\/p>\n\n\n\n
Homebrew, WinGet, and Linux package managers<\/h2>\n\n\n\n
If you used a package manager, use the package manager to remove it. Do not rm<\/code> a Homebrew-installed binary out from under Brew, or you will confuse brew doctor<\/code> forever.<\/p>\n\n\n\n
Homebrew has two casks. If you installed the stable channel:<\/p>\n\n\n\n
brew uninstall --cask claude-code\nbrew cleanup<\/pre>\n\n\n\n
If you installed the “latest” channel:<\/p>\n\n\n\n
brew uninstall --cask claude-code@latest\nbrew cleanup<\/pre>\n\n\n\n
The brew cleanup<\/code> line is not cosmetic. Brew keeps old versions around by default. Skip it and you will have Claude Code artifacts on disk long after you thought you removed them.<\/p>\n\n\n\n
WinGet:<\/p>\n\n\n\n
winget uninstall Anthropic.ClaudeCode<\/pre>\n\n\n\n
apt (Debian, Ubuntu):<\/p>\n\n\n\n
sudo apt remove claude-code\nsudo rm \/etc\/apt\/sources.list.d\/claude-code.list \/etc\/apt\/keyrings\/claude-code.asc<\/pre>\n\n\n\n
dnf (Fedora, RHEL):<\/p>\n\n\n\n
sudo dnf remove claude-code\nsudo rm \/etc\/yum.repos.d\/claude-code.repo<\/pre>\n\n\n\n
apk (Alpine):<\/p>\n\n\n\n
apk del claude-code\nsed -i '\\|downloads.claude.ai\/claude-code\/apk|d' \/etc\/apk\/repositories\nrm \/etc\/apk\/keys\/claude-code.rsa.pub<\/pre>\n\n\n\n
Removing the repository lines matters. Leave them behind, and your next system update will happily pull Claude Code back in as a “security update” if you ever reinstall by name. Ask me how I know.<\/p>\n\n\n\n
npm: the legacy path most people are still on<\/h2>\n\n\n\n
If you installed before the native installer shipped, or you followed a stale tutorial, you have the npm global package. This is now the legacy path, but it is the one I see most often on other people’s machines.<\/p>\n\n\n\n
npm uninstall -g @anthropic-ai\/claude-code<\/pre>\n\n\n\n
Two things to check afterward. First, run which claude<\/code> again. If npm was managed by nvm and you have multiple Node versions installed, the package might only be gone from the currently active Node. Switch versions (nvm use 20<\/code>, nvm use 22<\/code>) and re-run the uninstall for each one. This is the most common cause of “I removed it but the command still works.”<\/p>\n\n\n\n
Second, look at your shell rc file for a shell alias. Some early install scripts, and a few community wrappers, added a line like alias claude=\"npx @anthropic-ai\/claude-code\"<\/code> to ~\/.zshrc<\/code> or ~\/.bashrc<\/code>. That line survives the npm uninstall and will happily re-download Claude Code the next time you type claude<\/code>. Grep for it:<\/p>\n\n\n\n
grep -rn \"claude\" ~\/.zshrc ~\/.bashrc ~\/.bash_profile ~\/.profile 2>\/dev\/null<\/pre>\n\n\n\n
Delete anything that references Claude Code, source the file again, and open a new shell.<\/p>\n\n\n\n
Config files: the part everyone skips<\/h2>\n\n\n\n
None of the uninstall commands above touch your configuration. That is deliberate. If you plan to reinstall, you probably want to keep your MCP servers, your allowed-tools list, and your custom slash commands. If you are done with Claude Code, or you are troubleshooting a corrupted config by starting from zero, you have to delete these by hand.<\/p>\n\n\n\n
The user-level config on macOS, Linux, WSL:<\/p>\n\n\n\n
rm -rf ~\/.claude\nrm -f ~\/.claude.json<\/pre>\n\n\n\n
On Windows PowerShell:<\/p>\n\n\n\n
Remove-Item -Path \"$env:USERPROFILE\\.claude\" -Recurse -Force\nRemove-Item -Path \"$env:USERPROFILE\\.claude.json\" -Force<\/pre>\n\n\n\n
Project-level state lives inside each repo you used Claude Code in. From the project root:<\/p>\n\n\n\n
rm -rf .claude\nrm -f .mcp.json<\/pre>\n\n\n\n
What you are deleting, in order of “you probably do not want to lose this without a backup”: your OAuth session and any Anthropic auth tokens, your local settings including allowed tools and permissions, your MCP server configurations, your custom slash commands, session transcripts, and every CLAUDE.md context file<\/a> Claude Code has been reading. If any of that matters, copy ~\/.claude<\/code> to a tarball first.<\/p>\n\n\n\n
One trap. The VS Code extension, the JetBrains plugin, and the Claude Desktop app all write into the same ~\/.claude<\/code> directory. If you delete ~\/.claude<\/code> and any of those three is still installed, the directory rematerialises the next time you open them. If your goal is a truly clean state, remove the IDE plugins and the desktop app before you nuke the config.<\/p>\n\n\n\n
The IDE and desktop surfaces you probably forgot<\/h2>\n\n\n\n
Claude Code is not just the CLI. Every install method leaves side installs you might not remember.<\/p>\n\n\n\n
VS Code extension.<\/strong> If you ever ran Claude Code inside VS Code, or accepted the “install the Claude Code extension?” prompt, there is an extension. Remove it from the Extensions view (search “Claude Code”, click uninstall) or via the CLI: code --uninstall-extension anthropic.claude-code<\/code>.<\/p>\n\n\n\n
JetBrains plugin.<\/strong> Settings → Plugins → Installed. Search “Claude Code,” uninstall, restart the IDE. If you run JetBrains toolbox, it may cache the plugin per project; toolbox settings hold the state.<\/p>\n\n\n\n
Claude Desktop app.<\/strong> macOS: drag Claude.app<\/code> from \/Applications<\/code> to the Trash, then rm -rf ~\/Library\/Application\\ Support\/Claude<\/code> and rm -rf ~\/Library\/Caches\/Claude<\/code>. Windows: Settings → Apps → Installed apps → Claude → Uninstall. Linux: your package manager if you installed via one, otherwise remove the AppImage or the extracted binary.<\/p>\n\n\n\n
None of these are strictly Claude Code, but they all write to ~\/.claude<\/code> and any of them will keep the config directory alive if you forget. The full “is it really gone” check has to include them.<\/p>\n\n\n\n
One command per method: the reference table<\/h2>\n\n\n\n
Install method<\/th>Uninstall command<\/th>Config still there?<\/th><\/tr><\/thead>
Native installer (macOS\/Linux\/WSL)<\/td>rm -f ~\/.local\/bin\/claude && rm -rf ~\/.local\/share\/claude<\/code><\/td>Yes<\/td><\/tr>
Native installer (Windows)<\/td>Remove-Item \"$env:USERPROFILE\\.local\\bin\\claude.exe\"; Remove-Item \"$env:USERPROFILE\\.local\\share\\claude\" -Recurse<\/code><\/td>Yes<\/td><\/tr>
Homebrew (stable)<\/td>brew uninstall --cask claude-code && brew cleanup<\/code><\/td>Yes<\/td><\/tr>
Homebrew (latest)<\/td>brew uninstall --cask claude-code@latest && brew cleanup<\/code><\/td>Yes<\/td><\/tr>
WinGet<\/td>winget uninstall Anthropic.ClaudeCode<\/code><\/td>Yes<\/td><\/tr>
apt<\/td>sudo apt remove claude-code<\/code> (then remove repo list + key)<\/td>Yes<\/td><\/tr>
dnf<\/td>sudo dnf remove claude-code<\/code> (then remove .repo<\/code> file)<\/td>Yes<\/td><\/tr>
apk<\/td>apk del claude-code<\/code> (then remove repo line + key)<\/td>Yes<\/td><\/tr>
npm (legacy)<\/td>npm uninstall -g @anthropic-ai\/claude-code<\/code> (per Node version)<\/td>Yes<\/td><\/tr>
Config wipe (all methods)<\/td>rm -rf ~\/.claude ~\/.claude.json; rm -rf .\/.claude .\/.mcp.json<\/code><\/td>No<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Print this, tape it to your monitor, and never re-derive it from a Stack Overflow answer that was written in the npm era.<\/p>\n\n\n\n
Verify it is actually gone<\/h2>\n\n\n\n
The verification is not a formality. Open a new terminal, then run:<\/p>\n\n\n\n
claude --version\n# expected: command not found (or equivalent)<\/pre>\n\n\n\n
If you still get a version number, do these three things in order. First, which claude<\/code> and where.exe claude<\/code> to find the surviving binary; delete it. Second, grep -rn \"claude\" ~\/.zshrc ~\/.bashrc ~\/.bash_profile ~\/.profile ~\/.config\/fish\/config.fish 2>\/dev\/null<\/code> to catch aliases and PATH additions. Third, if you use nvm or asdf or fnm, iterate through every Node version and re-run npm uninstall -g @anthropic-ai\/claude-code<\/code> for each. That covers the three ways I have seen a “phantom” Claude Code survive an uninstall.<\/p>\n\n\n\n
Then check the config directory really is gone:<\/p>\n\n\n\n
ls -la ~\/.claude ~\/.claude.json 2>\/dev\/null\n# expected: nothing<\/pre>\n\n\n\n
If ~\/.claude<\/code> keeps coming back, the culprit is almost always the VS Code extension, the JetBrains plugin, or the Claude Desktop app respawning it. Kill those, delete the folder again, and it stays dead.<\/p>\n\n\n\n
When you should not uninstall<\/h2>\n\n\n\n
Half the time someone tells me they uninstalled Claude Code, they did not need to. If your goal is to fix an authentication problem, run claude logout<\/code> then claude<\/code> to re-auth. If your goal is to reset a broken config, delete ~\/.claude.json<\/code> alone and leave ~\/.claude<\/code> in place. If your goal is to switch models, use \/model<\/code> inside a session, or the autoUpdatesChannel<\/code> and minimumVersion<\/code> settings for version pinning. None of that requires a full removal.<\/p>\n\n\n\n
Uninstall makes sense in three specific cases. You are moving off Claude Code entirely, probably to Codex CLI or a different agent<\/a>. You are on a corporate machine and the security team told you to remove it. Or you are debugging something so deeply that a clean reinstall is faster than diagnosing the failure. Anything else, and the config wipe alone is enough.<\/p>\n\n\n\n
If you are removing Claude Code because you found it noisy in your editor or in your git history, that is a workflow problem, not a Claude Code problem. Fix the workflow first. My own guardrails post covers the PreToolUse hooks I run to stop the agent from writing to sensitive files<\/a>, which is the fix most people actually need. And if you are trying to decide between Claude Code and its competitors before you commit either way, the honest comparisons are in Cursor vs Copilot vs Claude Code<\/a> and the Copilot audit<\/a>.<\/p>\n\n\n\n
Frequently asked questions<\/h2>\n\n\n\n
Does npm uninstall -g @anthropic-ai\/claude-code<\/code> remove my Claude Code config?<\/h3>\n\n\n\n
No. The npm uninstall only removes the package binary. Your ~\/.claude<\/code> directory, ~\/.claude.json<\/code> file, any project-local .claude\/<\/code> folders, and .mcp.json<\/code> files are untouched. If you want them gone, delete them by hand. That separation is intentional, so a reinstall or a temporary removal does not blow away your MCP servers and session history.<\/p>\n\n\n\n
Why does claude<\/code> still run after I uninstalled?<\/h3>\n\n\n\n
Three usual causes. You have a second install through a different method, for example npm and native side by side. You have a shell alias in your ~\/.zshrc<\/code> or ~\/.bashrc<\/code> from an old install script. Or you use nvm or asdf and only removed the package from the currently active Node version. Run which claude<\/code> (or where.exe claude<\/code>) and grep -rn \"claude\" ~\/.zshrc ~\/.bashrc<\/code> to find the culprit.<\/p>\n\n\n\n
Is there a single “claude uninstall<\/code>” command?<\/h3>\n\n\n\n
Older native installer builds shipped a claude uninstall<\/code> subcommand that removed the binary and version files. The current documented path is the pair of rm<\/code> commands for ~\/.local\/bin\/claude<\/code> and ~\/.local\/share\/claude<\/code>. If claude uninstall<\/code> works on your version, use it. It does not remove config either way.<\/p>\n\n\n\n
How do I uninstall Claude Code on Windows?<\/h3>\n\n\n\n
If you installed with WinGet, run winget uninstall Anthropic.ClaudeCode<\/code>. If you used the PowerShell native installer, remove $env:USERPROFILE\\.local\\bin\\claude.exe<\/code> and the $env:USERPROFILE\\.local\\share\\claude<\/code> directory. To wipe config, also delete $env:USERPROFILE\\.claude<\/code> and $env:USERPROFILE\\.claude.json<\/code>. The Claude Desktop app is separate: uninstall it from Settings → Apps.<\/p>\n\n\n\n
How do I uninstall Claude Code on macOS?<\/h3>\n\n\n\n
Depends on how you installed. Homebrew: brew uninstall --cask claude-code<\/code> (or claude-code@latest<\/code>). Native installer: rm -f ~\/.local\/bin\/claude && rm -rf ~\/.local\/share\/claude<\/code>. npm: npm uninstall -g @anthropic-ai\/claude-code<\/code>. For a full removal, also run rm -rf ~\/.claude ~\/.claude.json<\/code> and drag Claude.app<\/code> to the Trash if you had the desktop app.<\/p>\n\n\n\n
Will uninstalling Claude Code cancel my Anthropic subscription?<\/h3>\n\n\n\n
No. Your Claude Pro, Max, Team, or Enterprise plan is a billing relationship with Anthropic, tied to your account. Deleting the CLI on your machine does nothing to it. To cancel, sign in at claude.ai and change your plan there. This is worth checking before you uninstall in a rage, because the two are unrelated.<\/p>\n\n\n\n
Should I back up ~\/.claude<\/code> before deleting it?<\/h3>\n\n\n\n
Yes if you have configured any MCP servers, written custom slash commands, or built up a set of allowed tools you would rather not re-approve. tar -czf claude-backup-$(date +%Y%m%d).tgz ~\/.claude ~\/.claude.json<\/code> is thirty seconds of insurance. On a clean reinstall you can restore the tarball and skip most of the setup.<\/p>\n\n\n\n