What Git can protect
- Committed source history, branches and tags
- Tracked project CLAUDE.md and .claude rules or skills
- Shared project configuration deliberately committed without secrets
- Collaboration through remote repositories
What usually sits outside Git
- Local Claude Code JSONL session transcripts
- Per-project auto memory stored under the user profile
- Personal settings, commands, agents and skills
- File history and other Claude-owned application state
- Uncommitted project files not covered by another backup
Use both layers
- 01
Keep code in Git
Commit and push meaningful work; back up important uncommitted files separately.
- 02
Protect Claude Code continuity
Back up supported local sessions, memory and customisations with credential exclusions and recovery proof.
- 03
Recover safely
Reconstruct local Claude Code state outside the live directory before reintroducing anything.
What Calmbu currently claims
Calmbu complements Git by protecting approved native Windows Claude Code workspace data while keeping known credentials and original project source files outside standard protection.
See the recovery model How Calmbu verifies its claimsCommon questions
If CLAUDE.md is committed, am I fully protected?
That protects the committed instruction file. It does not automatically include local transcripts, auto memory, personal settings or uncommitted work.
Can Calmbu repair Git history?
No. Use Git tools and your remote repository for Git history. Calmbu protects supported Claude Code workspace continuity around it.
Should .claude files be committed?
Project-scoped files can be committed when they are intentionally shared and contain no secrets. Personal user-level state remains separate.
Official references used for Claude Code facts
Anthropic documentation establishes Claude Code behaviour. Calmbu-specific statements describe the current product contract and are not presented as Anthropic guidance.