Version-Controlling My Home Folder CLAUDE.md

The Project

https://github.com/danielrosehill/Home-Folder-Claude-MD

Claude Code has a hierarchical configuration system: a CLAUDE.md file placed in your home directory applies to every Claude Code session launched anywhere beneath it. This makes the home-level CLAUDE.md a powerful tool for giving Claude persistent context about your machine, your preferences, and your identity. The challenge is that this file evolves constantly and has no built-in version control. This repository solves that.

What Goes in a Home-Level CLAUDE.md

My configuration file is extensive. It tells Claude who I am (name, location, timezone, contact info), what my machine looks like (Ubuntu with KDE Plasma on Wayland, Intel i7-12700F, AMD RX 7700 XT, 64 GB RAM), and how my local network is structured (OPNsense firewall at 10.0.0.1, Home Assistant at 10.0.0.3, NAS at 10.0.0.50). It specifies my development environment preferences: bash shell, nano for quick edits, VS Code as IDE, uv for Python, nvm for Node.

The file also sets behavioral expectations. When Claude is launched from the home directory rather than inside a specific repository, it should assume the task is general system administration. It should use speech-to-text tolerances (I dictate a lot and transcription errors are common). It should proceed autonomously on sysadmin tasks but ask before making significant architectural changes or deleting important data.

There is also a context directory system: the CLAUDE.md references separate files under ~/.claude/context/ for detailed information about the system environment, development tools, MCP usage, file organization, media tools, troubleshooting guides, and more. This keeps the main file manageable while allowing deep context when needed.

The Version Control Workflow

The repository is deliberately simple. It contains the canonical CLAUDE.md and a sync.sh script that performs a one-way copy from the repository to ~/CLAUDE.md. The workflow is: edit in the repo, run the sync script, commit and push. This gives full git history for every change to the configuration, easy rollback if something breaks, and a clean separation between the version-controlled source and the active file.

Why This Matters for Claude Code Users

The home-level CLAUDE.md is arguably the most impactful configuration file in the Claude Code ecosystem. It shapes every interaction on your machine. If you use Claude Code for system administration, having it understand your hardware, your network topology, and your preferences from the first message makes a significant difference. Without it, every session starts from zero context.

Version-controlling this file also provides a record of how your relationship with Claude Code evolves. Looking back through the git history, you can see when you added new context sections, when you refined behavioral instructions, and when you restructured the document as your understanding of what works deepened. It is a log of prompt engineering iteration applied to the most persistent prompt you have.