Removing Naetive from a computer
Last reviewed: 28 Oct 2026
Everything the installer put on this computer comes off with one command. Your account, your projects and their understanding live on Naetive and are untouched; you can sign in from anywhere afterwards. Claude Code and Node are yours and are left alone.
What is removed
- The Naetive connection registered with Claude Code (the
naetiveMCP server) and the hooks it added to Claude Code's settings. Claude Code itself stays. - Your key file under
~/.claude. - The console, the tunnel, the
naetivecommand and their launchers under~/.naetive. - This computer's pairing with your browsers. Pair again after a reinstall.
- The list of projects this computer shares, so nothing is shared from it any more. The folders themselves are untouched.
- On Windows with WSL, the shortcut in your Windows Startup folder that started Naetive at login.
Claude Code's settings file is backed up beside itself before anything is changed; the uninstaller prints where.
What is not
- Your projects and everything recorded on Naetive.
- Claude Code, Node, and anything else you installed yourself.
- A repository's
.naetive/folder. Delete it with the repository if you want it gone. - Your key on Naetive. Removing a computer does not change the key; if you think the key has been seen by someone else, use Regenerate under Settings on Connect as well.
Step 1: Stop what is running
Stop the tunnel with ~/.naetive/start-tunnel.sh --stop (on Windows, Ctrl+C in its window), close any chat open on the Chats page, then stop the console. The installer runs it in the background, so there is no window to close; this stops it:
macOS, Linux, WSL:
~/.naetive/start-console.sh --stop
Windows (PowerShell):
& "$env:USERPROFILE\.naetive\start-console.cmd" --stop
The uninstaller will not run while the console or the tunnel is up. It names which one is still running and the command that stops it, rather than end a process itself.
Step 2: Run the uninstaller
The command is on Connect, under Settings at the bottom, in Remove Naetive from this computer, and it is this:
macOS, Linux, WSL:
~/.claude/naetive-uninstall.sh
Windows (PowerShell):
powershell -NoProfile -ExecutionPolicy Bypass -File "$env:USERPROFILE\.claude\naetive-uninstall.ps1"
It asks no questions: it checks what is running, removes what it owns and prints what it left. On macOS, Linux and WSL it also accepts --yes, so a script or an agent can pass it; it does the same.
(Windows refuses to run .ps1 files by default; the -ExecutionPolicy Bypass part allows this one file, this once, and changes nothing else.)
It checks what is running, removes what it owns, and prints what it left in place and where the settings backup is.
Step 3: Check
Open Claude Code and run /mcp: naetive is gone. The uninstaller tells Naetive this computer is gone, so within a minute Connect shows nothing installed on this computer again (if it could not reach Naetive at that moment, Connect shows the console and tunnel as stopped until you run the installer again).
Putting it back
Run the installer from Connect again. It asks you to approve this computer in the browser, exactly like the first time.