Back up Codex on Windows
A practical, security-conscious guide to protecting local Codex sessions, configuration, skills, and other persisted state on native Windows.
Learn where Codex keeps local state, what Git does not cover, how to make a safer backup, and how to recover without overwriting the workspace you still have.
If you are comfortable maintaining the locations, exclusions, storage, retention and recovery tests, a manual backup can be a valid choice. Remember that keeping repeated full copies can multiply storage use as your local workspace grows.
Follow the safer DIY guideCalmbu packages supported scope, safer defaults, AES-256-GCM encryption, storage-efficient recovery points, plan-based automation and required recovery checks into one maintained product.
Each page answers one distinct recovery problem and links to the next useful decision.
A practical, security-conscious guide to protecting local Codex sessions, configuration, skills, and other persisted state on native Windows.
Understand CODEX_HOME, the default .codex folder, separate SQLite state, and which local Codex data needs special care.
A safe-folder-first recovery process for restoring local Codex state on Windows while leaving the active Codex home untouched.
Work out whether a deleted Codex session is recoverable, select the right earlier backup, and restore it without disturbing current sessions.
Move local Codex state to a replacement Windows PC without confusing repositories, credentials, and the Codex workspace layer.
Learn what Git protects, what Codex keeps outside a repository, and why developers need both source control and Codex-state recovery.
A concise checklist for testing whether native Windows Codex state, repositories, credentials, destinations, and recovery steps are genuinely covered.
These guides are useful now while Calmbu remains behind the public Windows download gate. The current Windows build supports approved native Windows workspace data for Codex and Claude Code. Codex in WSL, cloud-only ChatGPT/Codex data, credentials, and original project files remain outside current Codex coverage.
We distinguish what OpenAI documents from what Calmbu detects or tests. Pages are reviewed after meaningful Codex storage, Windows support, or Calmbu recovery changes. If a claim cannot be verified, it does not become a promise.
Read the evidence methodology