/home/hatch.
STORAGE SURVEY · 19 SEP 2026
What’s taking up the 38 GB?
Mostly temporary OpenClaw data, caches, agent runtime state, and duplicate backup material—not the documents and code worth protecting.
Filesystem + directory scan captured 2026-09-19 12:54 PM ET
The big buckets
Allocated size reported by the directory scan. The first bucket dominates the view.
Backup decision
The proposed repository is a durable-content backup, not a byte-for-byte image of a live machine.
Keep in hatch-repo
Human-authored material and the source needed to rebuild useful systems.
- Standing Markdown files, decisions, docs, memory, dreams
- Hooks, scripts, safe configuration, manifests
- Workspace projects, agent docs, artifacts, goals, source code
- Nested repository contents, with their Git metadata flattened out
Exclude as rebuildable
Large material that can be recreated or already has a separate backup path.
.openclaw-tmp, caches, session logs, runtime state- Python virtual environments and installed tool binaries
workspace/backupsand restore-test copies- Generated feed media and repository staging directories
Never commit
Private material that remains local even though the destination repository is private.
- SSH private keys and authentication tokens
- Telegram bot tokens and GitHub credentials
IDENTITY.mdand secret-bearing.envfiles- PEM/key files or anything matched by the secret scan
Complete directory ledger
Every top-level directory found in the scan, plus a second-level inventory of the workspace. Open each section for the full list.
/home/hatch — all top-level directories70.34 GB logical
/home/hatch/workspace — all first-level directories6.44 GB logical
Files directly in /home/hatch~96.5 MB
Inside the 6.44 GB workspace
The first four rows alone account for most of it. The durable, irreplaceable material is much smaller than the workspace total.
Daily backup sequence
The old repositories are retired only after the new backup is complete and verified.
Build the allowlist
Lock the meaningful subset and the exclusion rules before the first commit.
Run the secret gate
Block keys, tokens, credentials, environment files, and known private documents.
Push and verify
Create the private repository, push the curated tree, and confirm representative files are present.
Retire duplicates
Remove the three older GitHub repositories only after their content is confirmed inside the new one.