Uninstall

Use this page to remove Coven Code. Removing the binary, clearing Coven Code settings, and deleting shared Coven daemon state are separate steps. A routine uninstall usually removes only the package or binary.

Stop Running Sessions First

Exit the TUI before removing the binary. Removing Coven Code does not stop the coven daemon or end daemon-managed sessions. If you also want to stop background work, see CLI Uninstall -> Stop the daemon first.

Remove Npm Installs

For the Coven Code package:

npm uninstall -g @opencoven/coven-code

If you also installed the Coven daemon CLI and want it gone too:

npm uninstall -g @opencoven/cli

Then verify what remains on PATH:

which coven-code
which coven

On Windows, use where coven-code and where coven.

Remove Manual Binaries

If you installed from a release archive, remove the binary from wherever you placed it:

sudo rm /usr/local/bin/coven-code
rm ~/.local/bin/coven-code

If you installed into another directory, remove that copy instead. Check which coven-code first so you do not remove the wrong binary.

Remove Source Builds

If you installed with Cargo, remove the installed binary:

cargo uninstall claurst

If Cargo reports no installed package, inspect ~/.cargo/bin and remove only the Coven Code binary you installed.

Remove Coven Code State

Coven Code stores TUI-specific state under ~/.coven-code. Remove it only if you want to reset local Coven Code settings, account records, keybindings, plugins, and local session transcripts:

rm -rf ~/.coven-code

If you want a reversible reset, move the directory aside instead of deleting it.

Verify Removal

Confirm no Coven Code binary remains on PATH:

coven-code --version
which coven-code

If the command still exists, another install channel is present. Remove that channel too or leave it intentionally.

To reinstall later, use Install. If the reinstall opens but cannot connect providers or the daemon, see Troubleshooting.