Repository navigation
Description
What version of the Codex App are you using?
Windows Desktop 26.1117.3838.0. Both the Windows and WSL app-servers reported 0.171.0-alpha.13 in the Desktop logs.
What subscription do you have?
ChatGPT Plus.
What platform is your computer?
Windows x64, build 22621, with Ubuntu 22.04 on WSL2. I used WSL through the Windows desktop app and had not separately installed the standalone Codex CLI inside WSL.
What issue are you seeing?
After the November 20, 2026 update, four existing WSL projects still appeared in the sidebar, but all showed No chats. Their 12 main chats were still visible in Recents, where I could read their history. Custom chat titles had fallen back to text from earlier messages. New chats created in the same projects worked in WSL.
The older chats had originally run in WSL. After the update, Desktop still opened their existing entries through the Windows local host. Some showed a path like C:\home\<user>\<project> even though the original session metadata still contained /home/<user>/<project>. Desktop logs also showed thread/resume failures with error -32602 when a saved Linux workspace root was rejected by the backend handling the request.
I also saw a new authentication prompt and an integrated-terminal workspace warning after the update. I have not established whether those symptoms share the same cause.
What steps can reproduce the bug?
- Use the Windows desktop app in its legacy WSL mode with existing projects and chats. My repositories are under the Ubuntu home directory.
- Update to Desktop
26.1117.3838.0and let the WSL connection migration run. - Open an existing WSL project. In my case, the project showed No chats, even though its older chats were still in Recents.
- Open an old chat from Recents and try to resume it. Check the host and workspace path.
- Create a new chat in the same project as a control. The new chat should show the expected WSL host and Linux working directory.
A full application restart did not fix the old chats. I have not reproduced this on a fresh installation.
What is the expected behavior?
The migration should preserve the original thread IDs, history, custom titles, project associations, and side-chat relationships. An existing chat should still open from its project and resume on the correct WSL host. If the migration cannot move a thread safely, Desktop should report that and provide a recovery option.
Additional information
What I found
- The migration log reported
stage=completedfor four projects and one WSL distribution. Desktop then connected toremote-wsl:Ubuntu-22.04. - Desktop registered the projects on that WSL host, while the 12 older main chats remained on
localwithprojectId=null. The saved migration state showedprojectsMigrated=trueandthreadAssignmentsMigrated=false. - The Windows Codex store still held the original session files and title index. I also found four side chats with intact parent-thread IDs. The file data was recoverable.
- I created a new chat in one affected project as a control. It appeared under the correct project even though the WSL app-server's thread row had a null
project_id. Windows Desktop had a separate remote-project assignment for that chat containing the project ID and WSL host ID. That assignment was missing for the older chats.
These observations explain the host and project mismatch in my installation. I have not identified the exact client code path that left the migration incomplete.
Local recovery that worked
I backed up both Codex data stores and the Desktop user data, then tested one thread against an isolated WSL app-server. I stopped Desktop and both app-servers before applying changes to the real stores.
- I restored the original thread to the WSL Codex store with its original ID, account ownership, Linux working directory, and history. I verified that the WSL app-server could read its paginated history and list it after a restart.
- I restored the Desktop-side remote project assignment, using the freshly created chat in the same project as a control. This included the thread's entry in
thread-project-assignmentsand its WSL host inthread-project-membership-host-ids. Earlier tests that copied the history, set only the WSL databaseproject_id, or changed only the Desktop host hint did not restore the project entry. - After validating the first thread from the Desktop project sidebar, I repeated the process for the remaining chats. I restored the original custom names from the saved title index. For histories spanning multiple rollout files, I verified coverage by turn ID. For side chats, I preserved their original parent IDs and the source rollout segments needed to resume them.
- My first batch carried over the read-only permissions used during isolated testing. I corrected the affected threads using the app-server's
thread/settings/updatewith the:workspaceprofile andon-requestapproval policy. - I opened fresh integrated terminal tabs from the recovered chats. The workspace warning disappeared in the fresh terminals.
Result
I recovered 12 main chats and 4 side chats across all four projects. The main chats retained their original custom titles, and the side chats retained their original parent relationships. I verified that a recovered chat opened from its project and ran in Ubuntu with the expected Linux working directory. I also verified that all 16 WSL thread records had write access to their corresponding project directories and on-request approval.
After verifying the WSL copies, I archived the Windows copies using an operation scoped to the Windows local host. The original Windows history and backups were retained.
This was a version-specific local recovery that involved internal state. A supported repair or automatic migration for existing WSL chats would still be helpful.
Related reports
The duplicate bot flagged #62735, which appears to cover the same project-empty symptom after WSL migration. #60054 describes the closely related case where older WSL chats are resumed on the Windows backend. Please link or consolidate these reports if appropriate.
Activity
github-actions commentedon Nov 20, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
[-]Local projects no longer recognize existing conversations after update[/-][+][Windows 26.1117.3838.0] WSL workspace recognition broken after update — local projects show "No chats"[/+]rbnrong commentedon Nov 20, 2026
The
C:\home\…in your update is the detail I recognize from the same Windows package (26.1117.3838.0). On my installation the old chat still displayed its Linux workspace, but the Windows host had indexed the transcript and was handling the next turn. The workspace label and the terminal's current directory didn't tell me which host was actually running the chat. Opening old chats locally also appended settings events to the transcripts, so I wouldn't use a new turn in an original chat as the first diagnostic.Since you want to preserve the conversations, one check you can do on a backup is to follow a single affected thread's saved project assignment. Does it still name a local project whose root is
\\wsl$\<distro>\…? Is there also a remote project for that same distro and Linux path, with a different project ID? That pair was the clue for my empty sidebar. My assignment preview script reads the desktop state and counts those matches without opening any chat. It acceptsCODEX_HOME_WINpointing at the backup and defaults to dry-run.I didn't verify recovery of custom titles or the terminal warning. Those are worth tracking separately even if the project grouping comes back.
[-][Windows 26.1117.3838.0] WSL workspace recognition broken after update — local projects show "No chats"[/-][+][Windows][WSL] Desktop 26.1117.3838.0 moves projects to WSL but leaves existing chats on the Windows host[/+]