Updating

Before upgrading

1. Back up your data: snippbot reset --list-backups — or manually copy ~/.snippbot/
2. Check the changelog for breaking changes
3. Stop the daemon before upgrading

Upgrade

pip

# Stop the daemon
snippbot stop

# Upgrade
pip install --upgrade snippbot

# Restart
snippbot start

From source

snippbot stop

# Pull latest changes
git pull origin main

# Reinstall packages
source .venv/bin/activate
pip install -e packages/core packages/local packages/cli

# Rebuild UI
cd packages/ui && pnpm install && pnpm build && cd ../..

snippbot start

Docker

# Pull latest image
docker compose pull

# Recreate containers
docker compose up -d

# View logs to verify startup
docker compose logs -f snippbot

Verify the upgrade

snippbot --version
snippbot status
curl http://localhost:18781/health
snippbot doctor

Database migrations

Snippbot applies database migrations automatically on startup. If a migration fails:

# Check logs for migration errors
tail -50 ~/.snippbot/logs/daemon.log | grep -i migrat

# Restore from pre-upgrade backup if needed
snippbot reset --list-backups
snippbot reset --restore <backup-name>

Note

Database backups are created automatically before migrations run. Check ~/.snippbot/backups/ for the pre-upgrade snapshot.

Rollback

If the new version has a critical bug, roll back:

# pip — install specific version
pip install snippbot==0.4.1

# From source — check out previous tag
git checkout v0.4.1
pip install -e packages/core packages/local packages/cli

Always restore from a pre-upgrade backup when rolling back to avoid schema mismatches:

snippbot stop
snippbot reset --restore pre-upgrade-<timestamp>
snippbot start