Skip to content

Uninstall

Remove the CLI and everything it wrote.

On your machine

getstream uninstall

After a confirmation, this removes the state files under ~/.stream (your account session, the CLI's config, the cached version string) and then the binary itself. The skill and docs caches are kept, so skills already linked into projects keep working; pass --prune to remove those too. --force skips the confirmation and is required when there's no terminal to confirm in.

getstream uninstall --prune    # also remove the skill and docs caches
getstream uninstall --force    # no confirmation

Two things the command points out but can't do for itself: if the installer added ~/.local/bin to your PATH, remove that line from your shell profile; and if you ever ran the 0.1.x release, delete its stream binary too - running it would reinstall getstream.

On a CLI older than v1.3.0 the command doesn't exist. Remove the same things by hand:

rm "$(command -v getstream)"
rm -rf ~/.stream

In each project

Delete what the CLI wrote into project directories:

  • .stream/ holds the linked app's credentials. It's gitignored, so deleting it affects only your checkout.
  • The stream, stream-builder and stream-docs entries in .claude/skills/ or .agents/skills/ are symlinks into ~/.stream/skills/. They keep working after a default uninstall and break once the cache is gone (--prune or the manual rm -rf), so delete them when you remove the cache.

Any SDK key file written by getstream env belongs to your project; keep or delete it like any other file.

See also