CovenDocs
CLI ReferenceInstallUninstall

Uninstall

Uninstall reference for the Coven CLI across npm global installs, Cargo/source builds, and local state under COVEN_HOME.

3 min read

This page has platform-specific steps.

Use this page to remove the Coven CLI. A routine uninstall ends after you stop the daemon and remove the installed command. Local state under ~/.coven stays in place by default; deleting it is a separate, destructive final step.

Stop The Daemon First

The daemon holds the local socket and owns running sessions. Stop it before removing the CLI so nothing is left listening:

coven sessions --all --plain
coven daemon status
coven daemon stop

If sessions are still running, let them finish, kill them, or archive them first. Removing the CLI does not clean up a daemon that is already running.

Find Every Copy First

Machines that have been through more than one install route, or more than one Node version, usually carry more than one coven. Uninstalling only the copy you remember leaves the others answering. Ask Doctor before removing anything. In the CLI release that includes OpenCoven/coven#1124, it lists every copy on PATH, how each was installed, and the command that removes it. Until then, Doctor still prints the older path-only list; treat the block below as the forthcoming format:

coven doctor
Installs:
  [OK] ~/.local/bin/coven (active, this process) — npm, prefix ~/.local
  [!!] ~/.nvm/versions/node/v24.18.1/bin/coven (shadowed) — npm, prefix ~/.nvm/versions/node/v24.18.1
       remove: npm uninstall -g --prefix ~/.nvm/versions/node/v24.18.1 @opencoven/cli

Copies in a Node version that is not currently active do not appear on PATH; switch to that version (nvm use <version>), run npm prefix -g, and use npm uninstall -g --prefix <that-prefix> @opencoven/cli there too if you want them gone.

Remove The Install

Remove the CLI using the same method you installed with. Doctor's origin label tells you which one that is.

npm global install

A bare npm uninstall -g acts on the prefix of the currently active Node, which may not be the prefix that holds the copy you want gone. Name the prefix Doctor reported:

The command is the same in every shell:

npm uninstall -g --prefix <prefix> @opencoven/cli

When there is only one install and it is in the active prefix, the short form is equivalent:

npm uninstall -g @opencoven/cli

If you used npx/pnpm dlx for one-off runs, there is nothing to uninstall — clearing your package manager cache is enough to drop the downloaded copy.

Cargo / source build

If you installed the Rust binary with cargo install:

cargo uninstall coven-cli

If you only ran cargo build/cargo run from a cloned checkout, nothing was installed globally; deleting the checkout removes the build tree:

rm -rf coven   # the cloned OpenCoven/coven directory

Legacy coven-code installer alias

Older standalone coven-code installers wrote a coven alias into ~/.coven-code/bin. Doctor labels it legacy coven-code installer; delete that file. The current installer no longer creates it.

Native binary

If you placed a native binary on PATH yourself, delete that file from the directory you added to PATH. Then confirm nothing remains:

which -a coven

Verify Removal

macOS · Linux

which -a coven

Windows

Get-Command -All coven -ErrorAction SilentlyContinue

No output means PowerShell can no longer resolve the command. If a path or command record still prints, another install is still present — remove it with the matching method above.

Local State Is Preserved By Default

Coven keeps local state under COVEN_HOME (default ~/.coven), including session history, events, and the daemon socket. Uninstalling the CLI does not delete this directory. Routine uninstall stops here.

Deleting local state is irreversible

rm -rf ~/.coven permanently deletes your local session history and events. Do this only when you intend to erase all local Coven data, not as a routine uninstall or update step.

Delete Local State Only If You Intend To Erase It

Remove local state only as an explicit final action after the CLI is already gone:

rm -rf ~/.coven

If you set a custom COVEN_HOME, remove that path instead of ~/.coven.

Reinstalling Later

Removing the CLI while keeping ~/.coven lets you reinstall later and pick up your existing sessions:

npm install -g @opencoven/cli@latest
coven doctor

See Install Coven for full install paths and Install Debugging if the reinstall does not produce a working coven command.

Was this page helpful?No

Last updated on

On this page