clawdbot/docs/install/updating.md

summary, read_when

summary	read_when
Updating Clawdbot safely (npm or source), plus rollback strategy	Updating Clawdbot Something breaks after an update

Updating

Clawdbot is moving fast (pre “1.0”). Treat updates like shipping infra: update → run checks → restart → verify.

Before you update

• Know how you installed: npm (global) vs from source (git clone).
• Know how your Gateway is running: foreground terminal vs supervised service (launchd/systemd).
• Snapshot your tailoring:
  • Config: ~/.clawdbot/clawdbot.json
  • Credentials: ~/.clawdbot/credentials/
  • Workspace: ~/clawd

Update (npm install)

Global install (pick one):

npm i -g clawdbot@latest

pnpm add -g clawdbot@latest

Then:

clawdbot doctor
clawdbot gateway restart
clawdbot health

Notes:

• If your Gateway runs as a service, clawdbot gateway restart is preferred over killing PIDs.
• If you’re pinned to a specific version, see “Rollback / pinning” below.

Update (from source)

From the repo checkout:

git pull
pnpm install
pnpm build
pnpm ui:install
pnpm ui:build
pnpm clawdbot doctor
pnpm clawdbot health

Notes:

• pnpm build matters when you run the packaged clawdbot binary (dist/entry.js) or use Node to run dist/.
• If you run directly from TypeScript (pnpm clawdbot ... / bun run clawdbot ...), a rebuild is usually unnecessary, but config migrations still apply → run doctor.

Always run: clawdbot doctor

Doctor is the “safe update” command. It’s intentionally boring: repair + migrate + warn.

Typical things it does:

• Migrate deprecated config keys / legacy config file locations.
• Audit DM policies and warn on risky “open” settings.
• Check Gateway health and can offer to restart.
• Detect and migrate older gateway services (launchd/systemd; legacy schtasks) to current Clawdbot services.
• On Linux, ensure systemd user lingering (so the Gateway survives logout).

Details: Doctor

Start / stop / restart the Gateway

CLI (works regardless of OS):

clawdbot gateway stop
clawdbot gateway restart
clawdbot gateway --port 18789

If you’re supervised:

• macOS launchd (app-bundled LaunchAgent): launchctl kickstart -k gui/$UID/com.clawdbot.gateway
• Linux systemd user service: systemctl --user restart clawdbot-gateway.service
• Windows (WSL2): systemctl --user restart clawdbot-gateway.service

Runbook + exact service labels: Gateway runbook

Rollback / pinning (when something breaks)

Pin (npm)

Install a known-good version:

npm i -g clawdbot@2026.1.7

Then restart + re-run doctor:

clawdbot doctor
clawdbot gateway restart

Pin (source) by date

Pick a commit from a date (example: “state of main as of 2026-01-01”):

git fetch origin
git checkout "$(git rev-list -n 1 --before=\"2026-01-01\" origin/main)"

Then reinstall deps + restart:

pnpm install
pnpm build
clawdbot gateway restart

If you want to go back to latest later:

git checkout main
git pull

If you’re stuck

• Run clawdbot doctor again and read the output carefully (it often tells you the fix).
• Check: Troubleshooting
• Ask in Discord: https://discord.gg/clawd