---
title: Uninstall
description: Removing ClawMetry completely — what the uninstaller takes, what it deliberately leaves alone, per-platform notes, and how to keep your account.
keywords: clawmetry uninstall, remove clawmetry, clawmetry delete data, uninstall agent observability
eyebrow: Operations
---

# Uninstall

```bash
clawmetry uninstall
```

The command prints everything it is about to remove, then requires you to type
`uninstall` to confirm. Anything else — including an empty line, `y`, or
Ctrl-C — cancels.

:::danger This is irreversible
Your **encryption key** and cloud config are deleted with the rest of
`~/.clawmetry`. Without that key, snapshots already in the cloud cannot be
decrypted by anyone, including us — that is the point of
[end-to-end encryption](/docs/cloud/encryption/), and it is also why there is
no undo. If you intend to reinstall on this machine and keep reading old cloud
data, copy `~/.clawmetry/config.json` somewhere safe first.
:::

## What it removes

| Category | What |
|---|---|
| Daemons | Every `com.clawmetry.*` launchd job (macOS) or `clawmetry*.service` unit (Linux), plus any stray sync or dashboard process started by hand. |
| Config | `~/.clawmetry/` — including the encryption key, node id, license, cloud config and the local store. |
| State | The sync state file and the sync log. |
| Install | Venv installs at `/opt/clawmetry` and `~/.clawmetry`. |
| Symlinks | `/usr/local/bin/clawmetry`, `~/.local/bin/clawmetry`. |
| Package | `pip uninstall -y clawmetry`. |
| NemoClaw | Any detected NemoClaw sandbox: stops supervisord, removes the config, uninstalls the package inside the sandbox. |
| Registration | A background `POST /api/unregister` so the node stops counting against your plan. |

It stops daemons **before** deleting files, on purpose. The dashboard launchd
agent has `KeepAlive`, so a plist left registered would resurrect the server —
holding open files inside a directory the uninstaller had just deleted.

## What it deliberately does not touch

This is the part worth reading before you run it.

- **Your agents' own data.** ClawMetry reads
  `~/.claude`, `~/.codex`, `~/.openclaw`, `~/.cursor` and the rest read-only,
  and the uninstaller never removes them. Uninstalling ClawMetry does not
  cost you a single transcript.
- **Foreign hooks.** Where ClawMetry installed a pre-tool hook into a runtime's
  shared configuration, it marks the entries it owns and removes **only those**.
  Hooks another tool put in the same file are left exactly as they were.
- **Your ClawMetry account.** Uninstalling removes this *node*. It does not
  close your account or delete cloud history — see below.

## Your account survives

A node uninstall unregisters one machine. If you also want the account and its
data gone, that is a separate, explicit action:

| Goal | Do this |
|---|---|
| Remove this machine | `clawmetry uninstall` |
| Stop cloud sync but keep running locally | [`clawmetry nocloud`](/docs/start/deployment-modes/) |
| Delete the account and all cloud data | Account settings → Delete account |

Uninstalling on every node and assuming the account went with it is the common
mistake; the plan keeps billing until the account itself is closed.

## Platform notes

### macOS

Launchd jobs are booted out with `launchctl bootout gui/<uid>/<label>`, falling
back to `launchctl unload` on older releases, and the plist is removed. Venv and
symlink removal escalates to `sudo` only if a plain delete hits
`PermissionError`.

### Linux

Both scopes are handled — `systemctl --user disable --now` and the system-wide
equivalent — because a node may have been installed either way. Stray processes
are killed, then unit files are removed.

### Windows

There is no service manager involved; the daemon is a plain process or a
Scheduled Task child. Every ClawMetry process is stopped **first**, because
Windows cannot delete a file a live process holds open — a running daemon used
to make uninstall fail on its own `sync.log`.

`Scripts\clawmetry.exe` is a special case: pip cannot delete the very
executable the uninstall is running through. The uninstaller schedules a
detached delete that fires a moment after the process exits, so you are not
left with a zombie launcher that dies with `ModuleNotFoundError` on every
future invocation.

## If something is left behind

The uninstaller warns rather than lying. A locked file prints
`⚠️ Could not fully remove …` and the run continues — it never aborts halfway
and never prints a false success over a directory that is still there.

If you see that warning:

```bash
clawmetry status          # anything still running?
pkill -f clawmetry        # POSIX: stop what is left
rm -rf ~/.clawmetry       # then remove the directory by hand
```

On macOS, check for a plist that survived:

```bash
ls ~/Library/LaunchAgents/com.clawmetry.*
```

## Reinstalling

```bash
curl -fsSL https://clawmetry.com/install.sh | bash
```

or `pip install clawmetry && clawmetry`. A fresh install generates a **new**
encryption key and node id, so it appears as a new node in your fleet and
cannot read snapshots encrypted under the old key.

→ [Upgrades](/docs/ops/upgrades/) · [Plans and entitlements](/docs/ops/plans/) · [Local-only mode](/docs/start/deployment-modes/)