The latest articles on DEV Community by vild da (@vild_da_f524590ed3ae13840). https://dev.to/vild_da_f524590ed3ae13840 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3843027%2F810b8b05-f248-45e4-aec8-d965eb36d17d.png https://dev.to/vild_da_f524590ed3ae13840 en vild da Wed, 25 Mar 2026 10:50:42 +0000 https://dev.to/vild_da_f524590ed3ae13840/why-codex-history-disappears-after-switching-providers-and-how-i-fixed-it-f0j https://dev.to/vild_da_f524590ed3ae13840/why-codex-history-disappears-after-switching-providers-and-how-i-fixed-it-f0j <p>I ran into an annoying Codex problem while switching between official OpenAI auth and relay/custom providers.</p> <p>The sessions were not actually gone. What broke was session visibility.</p> <p>In practice, the symptoms looked like this:</p> <ul> <li>old sessions were visible under one provider, then disappeared after switching to another one</li> <li> <code>codex resume</code> and Codex App did not always show the same history</li> <li>changing only the rollout files was not enough</li> </ul> <h2> Why this happens </h2> <p>Codex stores provider-related session metadata in two places:</p> <ul> <li>rollout files under <code>~/.codex/sessions</code> and <code>~/.codex/archived_sessions</code> </li> <li>SQLite state in <code>~/.codex/state_5.sqlite</code> </li> </ul> <p>If only one layer is updated, the history may still look inconsistent. That is why a session can appear to be "missing" even though the actual data is still there.</p> <h2> What I built </h2> <p>I built <code>codex-provider-sync</code> to align both layers together.</p> <p>It can:</p> <ul> <li>inspect the current provider distribution</li> <li>sync rollout metadata and SQLite state to a target provider</li> <li>optionally update root <code>model_provider</code> in <code>config.toml</code> </li> <li>create a backup before each run</li> <li>restore from backup if needed</li> <li>skip locked live rollout files and report them clearly</li> </ul> <h2> Windows GUI </h2> <p>I also added a Windows GUI so normal users do not need Node or npm anymore.</p> <p>The GUI can:</p> <ul> <li>scan the current <code>.codex</code> home</li> <li>show provider distribution from rollout files and SQLite</li> <li>let you pick a target provider and execute the sync</li> <li>optionally update root <code>model_provider</code> </li> <li>restore from backup</li> <li>automatically keep the newest 5 managed backups by default, with configurable retention</li> </ul> <h2> Links </h2> <ul> <li>GitHub: <a href="https://github.com/Dailin521/codex-provider-sync" rel="noopener noreferrer">https://github.com/Dailin521/codex-provider-sync</a> </li> <li>Release: <a href="https://github.com/Dailin521/codex-provider-sync/releases/tag/0.2.0" rel="noopener noreferrer">https://github.com/Dailin521/codex-provider-sync/releases/tag/0.2.0</a> </li> </ul> <p>If you have hit the "my Codex history disappeared after switching providers" problem, this is exactly what the tool is meant to fix.</p> productivity