What Git is excellent at
- Committed source history and branches
- Collaboration through remote repositories
- Reviewable changes, tags, and releases
- Tracked project files such as repository-level AGENTS.md or .codex configuration when you intentionally commit them
What can sit outside the repository
- Codex sessions and history
- User-level config.toml and profiles
- Personal skills and reusable workflows
- SQLite-backed runtime state
- Authentication and logs
- Uncommitted files or worktrees that are not covered by your normal backup process
Use the two layers together
- 01
Keep code in Git
Commit and push meaningful source changes. Use a separate file backup for uncommitted work that must survive a device failure.
- 02
Protect supported Codex state separately
Back up the relevant CODEX_HOME state with credential handling, encryption, and recovery testing.
- 03
Recover into a safe folder first
Compare recovered Codex or worktree material against the repository before copying anything into active use.
What Calmbu currently claims
Calmbu is not a Git replacement or full-device backup. It protects supported native Windows Codex workspace data around Git-tracked code while keeping known credentials and unsafe or disposable material outside standard protection.
See the recovery model How Calmbu verifies its claimsCommon questions
If I push every commit, am I fully protected?
Your committed code history is protected by the remote Git repository, but user-level Codex sessions and configuration may still exist only on the PC.
Can Calmbu recover a broken Git history?
No. Use Git tools and your remote repository for Git-history problems. Calmbu's role is supported local Codex workspace backup and recovery.
Should project .codex files be committed?
Repository-scoped configuration can be committed when it is intentionally shared and contains no secrets. Personal user-level state under CODEX_HOME remains a separate concern.
Official references used for Codex facts
OpenAI documentation establishes Codex behaviour. Calmbu-specific statements describe the current product contract and are not presented as OpenAI guidance.