From da7a45b3a5695c445b67bf1277731817091df7d8 Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Sat, 24 Jan 2026 19:50:02 +0000 Subject: [PATCH] docs: clarify migration state vs workspace --- docs/help/faq.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/help/faq.md b/docs/help/faq.md index 98dba94f0..489c2265c 100644 --- a/docs/help/faq.md +++ b/docs/help/faq.md @@ -254,7 +254,9 @@ not a hard minimum. ### 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. 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 you’re in remote mode, remember the gateway host owns the session store and workspace. +**Important:** if you only commit/push your workspace to GitHub, you’re backing +up **memory + bootstrap files**, but **not** session history or auth. Those live +under `~/.clawdbot/` (for example `~/.clawdbot/agents//sessions/`). + Related: [Where things live on disk](/help/faq#where-does-clawdbot-store-its-data), [Agent workspace](/concepts/agent-workspace), [Doctor](/gateway/doctor), [Remote mode](/gateway/remote).