Before leaving the old PC
- Push committed source changes and preserve uncommitted files separately
- Record the active CODEX_HOME and any SQLite state override
- Create a current Codex-state backup and verify it
- Keep the recovery material separate from the old PC
- Record which work belongs to native Windows and which, if any, belongs to WSL
A safer migration sequence
- 01
Prepare the new Windows environment
Install the supported Codex surface and confirm the new PC uses the intended native Windows user profile.
- 02
Restore repositories separately
Clone or copy source repositories using your normal Git and file-backup process. Do not treat Codex state as a substitute for repository history.
- 03
Recover Codex state to a safe folder
Authenticate and validate the backup, then reconstruct it outside the new live CODEX_HOME.
- 04
Sign in again
OpenAI warns that file-based auth.json contains sensitive tokens. Prefer a fresh sign-in on the new PC instead of moving plaintext credentials.
- 05
Review settings, skills, and sessions
Check paths, project assumptions, permissions, and environment-specific configuration before adopting the recovered state.
- 06
Create a new verified backup
Once the new PC is working, establish a fresh recovery point tied to the new environment.
Migration is not the same as copying credentials
The valuable part of migration is continuity of supported local workspace state. Authentication should be re-established through the normal sign-in flow. This reduces the chance of exposing or reviving stale access tokens on another machine.
What Calmbu currently claims
Calmbu treats new-PC migration as recovery from a verified point. The current Codex migration path supports approved native Windows workspace data while repositories and fresh sign-in remain separate. Codex in WSL and cloud-only account data are excluded; Claude Code has its own supported coverage.
See the recovery model How Calmbu verifies its claimsCommon questions
Will Git move all of my Codex setup?
No. Git moves repository history and tracked files. User-level Codex sessions, settings, skills, and other state can live under CODEX_HOME and need a separate migration plan.
Should I copy auth.json to the new PC?
Prefer signing in again. OpenAI says file-based auth.json can contain access tokens and should be treated like a password.
Can I migrate from WSL with Calmbu?
No. The current Codex migration target is a supported native Windows Codex home.
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.