Your repository history
Commits, branches and tracked project files belong in Git. Keep using it.
Codex builds up local sessions, history, settings, skills and instructions that make work fast and resumable. Calmbu maintains agent-aware coverage for that supported workspace and verifies recovery.
A remote Git repository can restore your code. It does not automatically recreate the local Codex workspace that helped you understand, navigate and work on that code.
Commits, branches and tracked project files belong in Git. Keep using it.
Codex sessions, user-level settings, skills, instructions and history can live outside the repository Git protects.
If important Codex state exists only in your Windows profile, loss or failure of that device can take the working context with it.
A mistaken deletion, damaged profile or incompatible change can remove useful history before you realise you need an earlier point.
Cloning the repositories gets your code back. It may not bring back the supported Codex sessions, settings and workspace continuity around it.
A completed copy is not enough. Calmbu also checks that the encrypted recovery point is ready to recover.
Agent-aware coverage protects approved local workspace data around your repositories.
The backup is locked on your PC before it reaches the destination you choose.
The recovery point must pass Calmbu's private recovery checks before it is called Protected.
Calmbu can update and retest supported coverage when an agent changes.
Both plans encrypt, test, recover and migrate your supported Codex workspace. Choose how quickly new work becomes protected.
Pick a time. Calmbu creates and recovery-tests one automatic backup daily, with Back up now whenever you want an extra point.
Live Guard notices supported changes after a two-minute quiet period and respects the configured minimum interval between runs, which is two hours by default.
Calmbu runs on your Windows PC. Your readable Codex work is not sent to Calmbu for backup storage.
Calmbu separates documented Codex behaviour from claims proven by the current product.
Explore Codex backup and recovery guidesNo backup jargon. Just the things a Codex user should know.
Git protects committed repository history and tracked files. Codex also keeps supported user-level sessions, history and configuration outside a repository, so the two protections solve different problems.
Calmbu targets supported native Windows Codex state such as sessions, history, settings, skills, instructions and related user-created workspace state. Known credentials and disposable runtime files are excluded by default.
No. Calmbu reads and encrypts supported state locally, then writes the locked vault to the destination you choose. Your readable backup contents are not sent to Calmbu for cloud storage.
Yes. A verified recovery point can help reconstruct supported Codex state on another compatible Windows PC. Repositories and sign-in credentials should still be handled through their normal secure paths.
Set up Calmbu once. Keep building with a tested way back.
Download No administrator access · Windows 10 and 11 · One first recovery point before payment