docs: clarify migration state vs workspace

This commit is contained in:
Peter Steinberger
2026-01-24 19:50:02 +00:00
parent 15a9c21203
commit da7a45b3a5

View File

@@ -254,7 +254,9 @@ not a hard minimum.
### Can I migrate my setup to a new machine (Mac mini) without redoing onboarding? ### Can I migrate my setup to a new machine (Mac mini) without redoing onboarding?
Yes. Copy the **state directory** and **workspace**, then run Doctor once: Yes. Copy the **state directory** and **workspace**, then run Doctor once. This
keeps your bot “exactly the same” (memory, session history, auth, and channel
state) as long as you copy **both** locations:
1) Install Clawdbot on the new machine. 1) Install Clawdbot on the new machine.
2) Copy `$CLAWDBOT_STATE_DIR` (default: `~/.clawdbot`) from the old machine. 2) Copy `$CLAWDBOT_STATE_DIR` (default: `~/.clawdbot`) from the old machine.
@@ -264,6 +266,10 @@ Yes. Copy the **state directory** and **workspace**, then run Doctor once:
That preserves config, auth profiles, WhatsApp creds, sessions, and memory. If youre in That preserves config, auth profiles, WhatsApp creds, sessions, and memory. If youre in
remote mode, remember the gateway host owns the session store and workspace. remote mode, remember the gateway host owns the session store and workspace.
**Important:** if you only commit/push your workspace to GitHub, youre backing
up **memory + bootstrap files**, but **not** session history or auth. Those live
under `~/.clawdbot/` (for example `~/.clawdbot/agents/<agentId>/sessions/`).
Related: [Where things live on disk](/help/faq#where-does-clawdbot-store-its-data), Related: [Where things live on disk](/help/faq#where-does-clawdbot-store-its-data),
[Agent workspace](/concepts/agent-workspace), [Doctor](/gateway/doctor), [Agent workspace](/concepts/agent-workspace), [Doctor](/gateway/doctor),
[Remote mode](/gateway/remote). [Remote mode](/gateway/remote).