Uninstalling the Vibgrate CLI

If you need to remove the Vibgrate CLI from a machine, this guide covers a clean uninstall: signing out, removing the binary, and cleaning up project artifacts.

Step 1 — Sign out

If you logged in, clear the stored credential first:

vg logout

Step 2 — Remove the binary

Uninstall using the same tool you installed with.

npm:

npm uninstall -g @vibgrate/cli

pnpm:

pnpm remove -g @vibgrate/cli

yarn:

yarn global remove @vibgrate/cli

bun:

bun remove -g @vibgrate/cli

If you used the curl or PowerShell installer, delete the vg binary from the install directory that the installer reported, and remove that directory from your PATH if you added it manually.

Step 3 — Remove project artifacts

Vibgrate stores project settings and baselines in a .vibgrate directory created by vg init. If you no longer want them, delete that directory from each project. Removing it is safe and only affects local Vibgrate configuration and baselines.

Step 4 — Confirm removal

Verify the command is gone:

vg --version

If the command is no longer found, the CLI has been removed.

Per-project installs

If the CLI was a project dev dependency, remove it from that project instead of globally:

npm uninstall --save-dev @vibgrate/cli

Related

If you only meant to update rather than remove, see upgrading the Vibgrate CLI. To reinstall later, see the macOS and Linux or Windows install guides.