Varaverk/claude-data/projects/-root/memory/workspace.md

name, description, metadata

name	description	metadata
workspace	Primary workspace location and important paths	node_type type originSessionId memory project ffec43cd-13e3-4911-878f-40459f7d16a9

Primary workspace: /root

Plugin source: /boot/config/plugins/varaverk (on Unraid USB — persists across reboots)

Key files:

• /boot/config/plugins/varaverk/Notes_To-Do.md — running notes and design ideas
• /boot/config/plugins/varaverk/README.md — full project documentation
• /boot/config/plugins/varaverk/Manual.md — manual
• /boot/config/plugins/varaverk/common.sh — shared library
• /boot/config/plugins/varaverk/schedule.json — scheduling config
• /boot/config/plugins/varaverk/varaverk.cron — cron config

Claude Code Persistent Storage (as of 2026-06-13)

claude_startup.sh runs at array start and re-creates these symlinks every boot:

• /root/.claude → /boot/config/plugins/varaverk/claude-data/
• /root/.local/share/claude → /boot/config/plugins/varaverk/claude-bin/
• /root/.local/bin/claude → /boot/config/plugins/varaverk/claude-bin/versions/2.1.177
• /root/CLAUDE.md → /boot/config/plugins/varaverk/CLAUDE.md

Memory files live at: /boot/config/plugins/varaverk/claude-data/projects/-root/memory/

Old install data at /boot/config/claude and /boot/config/claude-bin has been fully migrated into claude-data and claude-bin — those old dirs can be deleted when convenient.

HOST1_STORAGE_MODE_INTERNAL=true in host1.conf controls all of the above.

Why: /boot is the Unraid USB drive and survives reboots/reinstalls. /root does not persist without explicit setup. How to apply: Always look at /boot/config/plugins/varaverk for the authoritative source. Notes and docs there survive power outages.