How to Completely Remove Claude Code: A Clean Uninstall Guide

Quick Answer: How Do I Fully Remove Claude Code? To completely remove Claude Code, you must uninstall it using the original installation method (npm, Homebrew, WinGet, or native installer), remove any IDE extensions (VS Code, JetBrains), delete the Claude Desktop app, and then manually clean up configuration files and cache directories including ~/.claude, ~/.claude.json, .claude/, and .mcp.json. If the claude command still runs afterward, a second installation or a shell alias is likely still present. ** Why a Full Cleanup Matters More Than Ever** Claude Code has grown rapidly from a research experiment into a mainstream developer tool. In early 2026, Anthropic reported that Claude Code reached billion‑product status within six months, while the MCP ecosystem hit 100 million monthly downloads. With the releases of Sonnet 4.6 and Opus 4.7, plus higher usage limits, Claude Code can now be installed in multiple places on the same machine.

That growth brings a practical problem: More installation surfaces = more leftover files.

If you are removing Claude Code for policy, security, cost, or workflow reasons, a partial uninstall is not enough. Leftover configuration files can cause unexpected behavior, recreate deleted directories, or interfere with other AI tooling.

Why Teams Are Moving Away from Local Claude Code Claude Code adoption has increased significantly, but so have the reasons for removing it.

1. Standardizing Developer Environments Engineering teams prefer reproducible, centralized AI infrastructure over machine‑specific tooling. Different Claude versions, permission states, MCP configurations, and shell aliases on individual laptops make environments hard to manage.

2. Reducing Local Agent Complexity Claude Code now interacts with terminals, IDEs, project directories, MCP servers, GitHub Actions, and autonomous workflows. Many organizations prefer thinner local environments.

3. Security and Compliance Enterprise requirements often include controlled API routing, centralized logging, vendor governance, and consistent model access. Removing local AI agents is a straightforward way to meet those policies.

4. Moving to API‑First Workflows A clear trend is emerging: teams are shifting from local AI tooling toward centralized API architectures. Instead of every developer maintaining their own AI agent, organizations adopt:

Unified AI gateways

Internal coding assistants

Backend orchestration systems

OpenAI‑compatible routing layers

This shift explains why unified API platforms are seeing increased interest among development teams.

Before You Start: Claude Code Lives in Multiple Places You may have installed Claude Code through:

Native installer

Homebrew

npm

WinGet

apt / dnf / apk

And separately installed:

VS Code extension

JetBrains plugin

Claude Desktop app

MCP integrations

Uninstalling only the CLI is rarely enough. ** Step‑by‑Step Uninstall Guide** Step 1: Identify Your Installation Method Installation Method Typical User Native installer Official Anthropic setup Homebrew macOS users npm JavaScript/Node developers WinGet Windows users apt / dnf / apk Linux package management IDE extensions VS Code or JetBrains users Step 2: Uninstall by Method Native Installer (macOS / Linux / WSL) bash rm -f ~/.local/bin/claude rm -rf ~/.local/share/claude Homebrew bash brew uninstall --cask claude-code ** or for the latest version** brew uninstall --cask claude-code@latest WinGet (Windows) powershell winget uninstall Anthropic.ClaudeCode npm bash npm uninstall -g @anthropic-ai/claude-code ⚠️ The npm package installs the same native binary as the standalone installer. npm uninstall alone does not remove config files, MCP settings, or IDE data.

Step 3: Remove IDE and Desktop Components VS Code Extension Open Extensions view → find “Claude Code” → Uninstall

Then delete global storage:

bash rm -rf ~/.vscode/globalStorage/anthropic.claude-code JetBrains (IntelliJ, WebStorm, PyCharm, etc.) Remove the plugin via the JetBrains Plugin Manager

Restart the IDE

Claude Desktop App Uninstall the desktop application before deleting shared configuration directories

Step 4: Delete All Configuration and Cache Files This is the most critical step.

On macOS / Linux / WSL bash rm -rf ~/.claude rm ~/.claude.json rm -rf .claude rm -f .mcp.json rm -rf ~/Library/Application\ Support/Claude On Windows (PowerShell) powershell Remove-Item -Path "$env:USERPROFILE.claude" -Recurse -Force Remove-Item -Path "$env:USERPROFILE.claude.json" -Force Remove-Item -Path ".claude" -Recurse -Force Remove-Item -Path ".mcp.json" -Force These directories store user settings, project settings, MCP server configurations, and session history.

Step 5: Verify Removal and Check for Leftovers Open a new terminal and run:

bash which claude # should return nothing On Windows:

powershell Get-Command claude # should return nothing If claude still resolves, check for:

A second installation in another location

An old shell alias (in .bashrc, .zshrc, .profile, or PowerShell profile)

Leftover PATH entries

Also search your system for any remaining .claude or .mcp.json files, especially inside old project directories.

Comparison: Which Uninstall Path Is Right for You? Install Path Uninstall Command Extra Cleanup Needed Native Remove ~/.local/bin/claude Config + IDE data Homebrew brew uninstall --cask claude-code Config + brew cleanup WinGet winget uninstall Anthropic.ClaudeCode Config + IDE data apt / dnf / apk Package remove + repo config removal Config + project files npm npm uninstall -g @anthropic-ai/claude-code Config + IDE data VS Code Uninstall from Extensions view Delete global storage Claude Code Alternatives: What to Use After Uninstalling Once Claude Code is fully removed, many teams realize they don’t actually need a local agent. They need reliable access to Claude‑quality models through a flexible, API‑first layer.

Comparison of Alternatives Tool Pricing Model Flexibility Best For Claude Code $20+/month subscription Anthropic only Agentic workflows CometAPI Pay‑per‑use, competitive Multi‑model (Claude, GPT, Gemini, etc.) Cost‑conscious teams, unified API Cursor Subscription Multi IDE users Aider / OpenCode Open‑source + BYOK Any model Privacy‑focused, no vendor lock‑in Gemini CLI Google pricing Google models Free‑tier users Why a Unified API Approach Makes Sense After removing a locally installed agent like Claude Code, you still need access to high‑quality models for:

Backend automation

Internal tools

Product features

CI/CD integrations

A unified API platform gives you:

No vendor lock‑in – switch between Claude, GPT, Gemini, and others with one integration

Better cost control – pay only for what you use

Higher throughput – avoid per‑user or hourly caps

One consistent interface – no need to learn different SDKs for every model

FAQ How do I completely clean remove Claude Code? Follow the platform‑specific uninstall steps above, then manually delete ~/.claude, ~/.claude.json, .claude/, and .mcp.json.

Does uninstalling Claude Code remove my authentication tokens? Yes, manually deleting the ~/.claude directory removes auth tokens and session data.

Can I remove Claude‑related watermarks from generated code? Yes, using standard text processing tools like sed or dedicated post‑processing scripts.

Is Claude Code still worth using in 2026? It depends on your workflow. Many developers and teams are moving toward API‑first, multi‑model platforms for greater flexibility and cost predictability.

Conclusion: A Clean Slate and Smarter AI Workflows Removing Claude Code completely gives you control over your local environment and opens the door to a more flexible, API‑driven approach to AI‑powered development. A thorough uninstall removes not just the binary but also configuration drift, hidden caches, and accidental reinstall paths.

Once you have a clean slate, you can build more resilient, cost‑effective, and model‑agnostic AI workflows — without being tied to a single vendor or a locally installed agent.