Skip to main content
Uninstall in this order so the CLI can remove the integration it created.
Removing the CLI is a local action. It does not delete your Clawdi account, server-side data, Project memberships, or Cloud Agents.
Before uninstalling, record the current local paths while the CLI is still available:
1

Stop and remove the background daemon

This removes the per-user service unit and stops the local sync daemon.
2

Remove Connected Agent integration

Review the registered Agent software, then remove all local registrations, bundled Skills, and supported MCP entries:
Use --agent <software> instead of --all to remove only one Connected Agent integration.
3

Sign out this computer

Sign-out removes the locally stored login and cached environment credentials. If CLAWDI_AUTH_TOKEN controls the current process, unset it separately.
4

Remove the executable

Confirm command -v clawdi points into ~/.local, then remove the launcher and native release directory:
If you used CLAWDI_INSTALL_PREFIX, replace ~/.local with that exact prefix. Do not remove a path until you have confirmed it belongs to the Clawdi native installer.

​
Decide whether to keep local state

Clawdi keeps local configuration, logs, and sync state under ~/.clawdi by default. This directory remains after removing the executable unless you move or delete it explicitly. If you want a recoverable local cleanup, move the directory out of the way instead of deleting it immediately:
This local directory is separate from data stored in your Clawdi account. For an account or server-side data request, contact Support and do not send credentials or Vault values.
Last modified on August 2, 2026