Uninstall

Uninstalling is clean and reversible. The adapters touch only BirdyBeep-managed entries, so removing them leaves the rest of your harness config exactly as it was.

Remove integrations

birdybeep agent uninstall all      # remove only birdybeep-managed entries
birdybeep agent uninstall claude   # remove from a specific harness

This removes the managed hook/plugin entries from ~/.claude/settings.json, ~/.codex/config.toml, ~/.config/opencode/opencode.json, and ~/.cursor/hooks.json — your own hooks and config are preserved. Installs also kept a one-time backup alongside each file.

Revoke the machine

To fully disconnect a machine, revoke it from the app (Machines → revoke). That immediately invalidates its token and drops its sessions server-side. To remove all of your data, see the account deletion page.

Remove the CLI

npm rm -g @birdybeep/cli

The CLI stores no secrets in its package; your machine token lives in the OS keychain and is cleared on revoke.