Everything ClawBox cares about lives under /home/clawbox. The app itself is a git checkout; all personal state is deliberately kept outside tracked files so updates can hard-reset the code without touching your data.
Rows marked OpenClaw/dual or Hermes/dual exist only on those editions. Check yours with cat /etc/clawbox/edition.env.

​
Map

​
Credentials — exactly where secrets live

​
What survives what

The update mechanism achieves this with git reset --hard <release> + git clean -fd (note: no -x — gitignored paths like data/ and .env are never cleaned). Details: Update System. Every ❌ row above assumes the path really is the directory it names. If one of them has been replaced by a symlink, the factory reset removes the link and leaves whatever it pointed at alone — it never deletes through it — and reports the reset as incomplete, naming the path, without clearing the Wi-Fi, resetting the login password or rebooting. So the box stays reachable and the redirected store is still there to deal with. A plain file where a directory belongs is simply removed and the reset finishes normally.
Do not hand-roll a factory reset over SSH from this table. rm -rf ~/.hermes deletes hermes-agent/ and bricks the Hermes harness; rm -rf data/* deletes network.env and the offline model weights. The safe procedure is Recovery → D.

​
~/.hermes/config.yaml is generated state

On the Hermes edition several ordinary product actions rewrite that file end to end:
  • hermes config set, which ClawBox shells out to from Settings → Local AI (three calls per save) and from the Telegram flow;
  • scripts/register-mcp.sh, at every web-server boot;
  • scripts/setup-hermes-dashboard-auth.sh, as the dashboard unit’s ExecStartPre.
Each one does a full load → serialize → save, so hand-added comments and formatting are not preserved — including the commented Security and Fallback-Model blocks the file ships with. Saving a local model in the ClawBox UI is enough to strip them. Treat the file as generated: keep your own notes elsewhere, and let the writers serialise through ~/.hermes/config.yaml.lock rather than editing it under them.

​
Logs