Updating & Uninstalling

Updating EdgeCrab

From crates.io

cargo install edgecrab-cli --force

The --force flag reinstalls even if the same version is already present. After the build completes, your config, memories, and skills in ~/.edgecrab/ are untouched.

Pre-built Binary

Download the latest archive from GitHub Releases and replace the binary:

# macOS / Linux — replace in place
sudo cp edgecrab /usr/local/bin/edgecrab
edgecrab version

Docker

docker pull ghcr.io/raphaelmansuy/edgecrab:latest

docker-compose:

docker compose pull
docker compose up -d

Source Build

cd edgecrab
git pull origin main
cargo build --release

Check Your Current Version

edgecrab version
# EdgeCrab 0.1.0  (rustc 1.85.0, 2025-02-20)

Uninstalling EdgeCrab

1. Remove the binary

# If installed via cargo
cargo uninstall edgecrab-cli

# If installed as a pre-built binary
rm /usr/local/bin/edgecrab

2. Remove configuration and state (optional)

rm -rf ~/.edgecrab

3. Remove shell completions (if installed)

rm ~/.zsh/completions/_edgecrab         # zsh
rm ~/.local/share/bash-completion/completions/edgecrab  # bash
rm ~/.config/fish/completions/edgecrab.fish              # fish

Backing Up Your Data

Before updating or uninstalling, back up your user data:

cp -r ~/.edgecrab ~/.edgecrab.bak

Your data includes:

~/.edgecrab/config.yaml — provider settings and preferences
~/.edgecrab/memories/ — persistent agent memory files
~/.edgecrab/skills/ — custom and learned skills
~/.edgecrab/state.db — full session history (SQLite)

Migrating to a New Machine

Copy ~/.edgecrab/ to the new machine
Install EdgeCrab (any method above)
Run edgecrab doctor to verify API keys are set

If moving from Hermes Agent, use edgecrab migrate instead — see Migrating from Hermes.

Staying Up to Date

EdgeCrab follows semantic versioning. Breaking changes are announced in the Changelog.

Subscribe to releases: Watch the GitHub repository → “Releases only” to be notified of new versions.

Automated update check (coming soon): EdgeCrab will optionally notify you when a new version is available on startup. Disable with display.check_for_updates: false.

Frequently Asked Questions

Q: Will updating overwrite my config, memories, or skills?

Never. Updates only replace the binary — ~/.edgecrab/ is never touched. Your full session history, memories, skills, and config survive all updates.

Q: Do I need to re-run edgecrab setup after updating?

No, unless the update adds new required config fields (rare, always documented in the changelog). Run edgecrab doctor to catch any new issues.

Q: How do I update to a specific version, not the latest?

cargo install edgecrab-cli --version 0.1.0 --force

For pre-built binaries, download the specific tag from GitHub Releases.

Q: The new version has a new config option I want to use. How do I add it?

edgecrab config set memory.auto_flush true

Or open ~/.edgecrab/config.yaml in your editor. New options use defaults if not present — you only need to set them if you want non-default behavior.

Q: Can I roll back to the previous version?

Yes. Re-install any previous version from crates.io or download the binary from GitHub Releases. Your data is always compatible across patch versions and usually across minor versions (see changelog for exceptions).