Steroid Kit logo

Steroid_Kit

Steroid CLI›Updating & Uninstalling

Updating & Uninstalling

The Steroid CLI manages its own updates and can cleanly remove itself when needed. No package manager required — everything is handled by the binary itself.

Self-Update

Run steroid update to check the latest GitHub release and apply it. Replacement differs between POSIX and Windows; do not assume an atomic rename or automatic startup-health rollback.

Update command

steroid update
  1. Resolves the GitHub releases/latest redirect and compares versions.
  2. Downloads the platform release asset. The updater has separate macOS arm64/x86_64, Linux and Windows asset selection.
  3. Checks SHA-256 when a checksum sidecar is published; this implementation does not perform GPG verification.
  4. On POSIX, backs up the executable as steroid.bak and copies the replacement. Windows stages a batch-file swap.
  5. Attempts to refresh the daemon on a best-effort basis. Check the installed version and diagnostics afterward.

Inspect the installed update

steroid --version
steroid doctor
steroid daemon status

NOTE

Installer scripts are maintained outside these repositories. Their architecture/signature behavior must be checked independently; the updater implementation is not evidence of installer guarantees. Restart IDE MCP processes when they still run the previous executable.

Manual rollback (if needed)

# POSIX, for the standard ~/.steroid/bin installation.
# Confirm the backup exists and stop relevant clients before replacing.
cp ~/.steroid/bin/steroid.bak ~/.steroid/bin/steroid
steroid daemon start --force
steroid --version

Uninstall

Use the supported uninstaller rather than guessed OS service names or broad manual deletion. Uninstall removes Steroid state, credentials and owned IDE wiring/managed skills. Source conversation history is not the derived index. The separate onboarding bootstrap intentionally survives.

Interactive uninstall

Review the confirmation before proceeding

steroid uninstall

Noninteractive uninstall

Only after reviewing what will be removed

steroid uninstall --yes

WARNING

Back up needed data before uninstalling. A recoverable local Vault backup needs both cryptfile_pass.cfg and .cryptfile_key, together with credentials_index.json. Protect the backup like plaintext credentials: the password material permits decryption. There is no vault export command. Local uninstall does not revoke third-party tokens or delete published cloud flows/AP Connections.

On this page