Uninstall

burrowee uninstall removes the managed service and clears the CLI's state from your machine. By default it is non-destructive: your pairing is backed up, not deleted, so you can change your mind.

Backup mode (the default)

burrowee uninstall

This removes the managed service first — the system unit, plus any legacy per-user unit from an older release — which stops the managed daemon. Then it moves your state home aside rather than deleting it:

• ~/.burrowee/cli is renamed to ~/.burrowee/cli.bak.<timestamp> (e.g. cli.bak.20260612-153045) — config and pairing credentials all preserved;
• the daemon's transport socket is removed.

backed up /home/you/.burrowee/cli → /home/you/.burrowee/cli.bak.20260612-153045
removed transport socket ~/.burrowee/cli/sockets/transport.sock

Running it again when there's nothing left is a harmless no-op (nothing to back up at …).

To restore a backup, just rename the directory back:

mv ~/.burrowee/cli.bak.20260612-153045 ~/.burrowee/cli

Purge mode

burrowee uninstall --purge

Purge deletes everything outright: the state home and every prior *.bak.* backup, printing one removed … line per path. There is no recovery — your pairing keys are gone, and re-pairing requires the gateway operator's involvement (below). Use it when you're decommissioning a machine or handing it to someone else.

Flags

Flag	Meaning
--purge	delete all files instead of backing up state
--home <dir>	cli state dir to uninstall (default ~/.burrowee/cli)
--config <path>	config.json path; its parent dir is used as the home (overrides --home)

What it doesn't do

• A daemon you run under your own supervisor (tmux, a custom unit, a foreground burrowee daemon) is never touched — stop it yourself (Ctrl-C or kill). Only the managed units uninstall wrote are removed.
• The binaries stay on disk; remove them the way you installed them (see Install).

Re-pairing afterwards

After a backup-mode uninstall, restoring the directory brings the old pairing back as-is. After a purge, you start over: the gateway operator should revoke the old client pairing in the gateway's local console (your old key can no longer be used, but tidiness counts), mint a fresh blob + PIN, and you run burrowee bootstrap again.