Codex Windows App reported an error after upgrading: Codex cannot access its local database #23780

Activity

1. davidjqq19

   added

   appIssues related to the Codex desktop appIssues related to the Codex desktop app

   on May 20, 2026
2. github-actions

   added

   bugSomething isn't workingSomething isn't working

   windows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems

   configIssues involving config.toml, config keys, config merging, or config updatesIssues involving config.toml, config keys, config merging, or config updates

   on May 20, 2026
3. github-actions commented on May 20, 2026

   

   github-actionsbot

   on May 20, 2026 – with GitHub Actions

   Contributor

   More actions

   Potential duplicates detected. Please review them and close your issue if it is a duplicate.

   • Windows Desktop WSL app-server fails to launch due to CRLF/LF SQLx migration checksum mismatch #23777
   • WSL CLI cannot share Windows Codex App CODEX_HOME: migration 1 was previously applied but has been modified #23251

   Powered by Codex Action
4. davidjqq19

   closed this as completedon May 20, 2026
5. davidjqq19

   changed the title [-]The Codex Windows app crashes and becomes impossible to reopen after setting the agent environment and terminal environment to WSL and then closing the app[/-] [+]Codex Windows App reported an error after upgrading: Codex cannot access its local database[/+] on May 20, 2026
6. miku-lilac

   marked Codex Desktop fails to start with migration 1 was previously applied but has been modified #23824 as a duplicate of this issue on May 21, 2026
7. xdifu commented on May 23, 2026

   

   xdifu

   on May 23, 2026

   Last edited by xdifu

   More actions

   This is the same root-cause family as #23777 / #23787: the WSL/Linux Codex backend rejects a Windows-created SQLite DB because SQLx migration checksums differ at the CRLF-vs-LF byte level. Moving state_5.sqlite* / logs_2.sqlite* aside is a launch workaround, but it forces Codex to rebuild metadata instead of repairing the existing DBs.

   For users who want to preserve local history metadata, I published a non-destructive repair tool: https://github.com/xdifu/codex-repair

   Windows PowerShell / Windows Terminal:

   git clone https://github.com/xdifu/codex-repair.git
   cd codex-repair
   python codex-repair.py fix --apply

   If you run it from WSL bash to repair Windows Codex Desktop data, pass --codex-home "/mnt/c/Users/<WindowsUser>/.codex" so it does not target WSL's own ~/.codex.

   It backs up the SQLite DBs, extracts the active backend's expected checksums, schema-verifies before rewriting _sqlx_migrations, and leaves ~/.codex/sessions/*.jsonl read-only.