Uninstalling SuperClaude | Remove All Config Files Without a Trace

Before Uninstalling: SuperClaude Has Two Layers

To cleanly remove SuperClaude, you first need to understand its structure. SuperClaude consists of two distinct layers:

• The Python package itself: The SuperClaude package installed via pip, pipx, or npm. This is the actual installer and CLI command.
• Config files: Behavior instructions and command definitions placed in the ~/.claude/ directory. These are deployed when you run SuperClaude install.

This means that removing only the package with pip uninstall still leaves the config files under ~/.claude/ in place. Conversely, manually deleting just the config files still leaves the package in your environment. Removing both in the correct order is the key to leaving nothing behind.

Note that the current stable version is v4.3.0 (released March 22, 2026). Minor CLI behavior may vary between versions, so when in doubt, always refer to the official repository as the authoritative source.

The Basic Uninstall: Done in 2 Steps

The official installation guide's recommended complete removal process consists of 2 steps. Order matters — run the SuperClaude cleanup first, then remove the package itself last.

1. Run the SuperClaude uninstaller to remove config files deployed to ~/.claude/: SuperClaude uninstall
2. Remove the Python package itself: pip uninstall SuperClaude

The reason this order is important is that the SuperClaude uninstall command knows which config files it placed during installation and removes exactly those. If you remove the package first, the CLI that performs this cleanup no longer exists, and the config files are left stranded.

Source: Installation Guide (Uninstall section)

Removal Commands for pipx / npm Installations

Because SuperClaude can be installed in multiple ways, the basic rule is to uninstall using the same package manager you used to install it. The step of running SuperClaude uninstall first is the same regardless — only the final package removal command differs depending on how it was installed.

• Installed with pip: Run SuperClaude uninstall, then pip uninstall SuperClaude
• Installed with pipx: Run SuperClaude uninstall, then pipx uninstall SuperClaude
• Installed with npm: Run SuperClaude uninstall, then npm uninstall -g @bifrost_inc/superclaude (include -g to remove the global installation)

The npm package name may change due to distribution reasons. If npm uninstall returns an error, run npm list -g to check the actual SuperClaude-related package name installed, then specify that name. For pipx, you can similarly verify the installed name with pipx list.

Verify What Remains in ~/.claude/ After Removal

SuperClaude uninstall is designed to clean up the files it placed, but it's reassuring to confirm with your own eyes that everything is actually gone. According to the official guide, SuperClaude places files like the following in ~/.claude/:

• Framework core files (approximately 50MB in total)
• ~/.claude/CLAUDE.md (the main entry-point instruction file, approximately 2KB)
• Behavior instruction files (approximately 200KB)
• ~/.claude/claude-code-settings.json (MCP server integration settings, approximately 5KB)

After uninstalling, check the contents of ~/.claude/ with something like ls -la ~/.claude/ to confirm none of these remain. If any SuperClaude-originated files are clearly still present, refer to the troubleshooting section below.

Most Important Warning: Do Not Delete ~/.claude/ Entirely

This is the most common trap — and it's one you can't easily undo. ~/.claude/ is not a SuperClaude-exclusive folder; it is a shared directory also used by Claude Code itself. Your own CLAUDE.md notes and various Claude Code settings all live inside it.

Therefore, deleting the entire directory with something like rm -rf ~/.claude/ because you "want to leave no config files behind" will erase not just SuperClaude but your personal Claude Code settings as well. This is precisely why the SuperClaude uninstall command exists. The uninstaller selectively removes only what SuperClaude added, leaving the shared directory's other contents intact.

Even if you insist on removing files manually, avoid deleting the entire directory. Remove only the files that SuperClaude generated individually. When in doubt about a file, leave it in place — that is the safer choice.

Just in Case: Back Up Before Deleting

If you've put effort into customizing your setup and want to be safe before uninstalling, you can create a backup first. SuperClaude provides a dedicated backup command for this purpose.

1. Back up the current state: SuperClaude backup --create
2. Restore when needed: SuperClaude backup --restore [file] (specify the file path shown when the backup was created, e.g., SuperClaude backup --restore ~/superclaude_backup_20260606.tar.gz)

By keeping the backup file created with --create, you can use --restore to bring your settings back even after uninstalling — for those moments when you change your mind. It's a worthwhile step to take before making major environment changes.

Source: Installation Guide (Backup section)

Troubleshooting When Uninstall Doesn't Go Smoothly

Even following the steps correctly, errors or leftover files can sometimes occur depending on your environment. Here are the most common issues and how to handle them.

• SuperClaude: command not found appears: In most cases, the package was removed before running the uninstaller. In this situation, reinstall the package with pip install SuperClaude (or pipx), run SuperClaude uninstall, and then remove the package again.
• SuperClaude-originated files remain in ~/.claude/: Re-run SuperClaude uninstall. If files still remain, refer to the list in the "Verify what remains" section above and delete only the SuperClaude-placed files individually. Do not delete the entire shared directory.
• Permission errors prevent removal: When installed globally with pipx or npm -g, elevated permissions may be required depending on your environment. Check the permission conventions for your package manager.
• You don't remember how it was installed: Run pip show SuperClaude, pipx list, and npm list -g in turn, and uninstall using whichever package manager shows a match.

The fundamental rule for troubleshooting is to never break the order: "first clean up config with SuperClaude uninstall, then remove the package."

If You Want to Reinstall After Uninstalling

If you remove SuperClaude and later decide you want to use it again, simply follow the normal installation steps to set it up once more. With pipx, install the package with pipx install SuperClaude, then run SuperClaude install to redeploy the components. If you made a backup beforehand, you can also restore your previous settings with SuperClaude backup --restore.

If you want to clean up only part of the installation rather than removing everything, SuperClaude lets you specify components at install time, such as SuperClaude install --components core mcp modes. If you need fine-grained options at uninstall time, run SuperClaude uninstall --help to see the available choices at that point.

Summary

Uninstalling SuperClaude comes down to a 2-step process: clean up config files with SuperClaude uninstall, then remove the package with pip (or pipx / npm). The most important thing to remember is that ~/.claude/ is a directory shared with Claude Code itself — never delete it wholesale with rm -rf. Using the dedicated SuperClaude uninstall command allows you to safely remove only what was added, without collateral damage. Taking a backup with SuperClaude backup --create before you start means you can always restore your setup if you change your mind. Since minor CLI behavior can vary between versions, always check the official repository for the definitive steps.

Source: SuperClaude_Framework (GitHub) / Installation Guide