You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Windows][WSL] Automatic migration leaves projects with no chats despite intact Windows history #62735
Use the Windows desktop app with the legacy WSL agent environment and existing project chats.
Update and relaunch on an installation that receives the automatic migration to WSL remote connections.
Expand the migrated projects after WSL: Ubuntu connects.
Actual behavior
Four projects were switched to WSL: Ubuntu. The project entries remained visible and the connection showed as connected, but the projects showed “No chats” in both the ChatGPT and Codex views.
The desktop log recorded [wsl-migration] with stage=completed and singleFolderProjectCount=4. For one affected project, I matched 47 historical project assignments to readable Windows session files. Of those, 36 were in the active sessions directory and 11 were in the archive. The Ubuntu session database used by the new connection contained none of those 47 thread IDs, and the old local project assignments were absent from the current desktop state.
Expected behavior
Existing active chats should remain accessible under the project after the automatic migration, with archived chats retaining their archived status. If the migration keeps the chats on the original host, the desktop app should preserve a way to find them through the project or provide a supported recovery flow for installations that have already migrated.
Related to #60054, which reports old chats failing to resume after the same type of migration. The symptom here is an empty project chat list despite the original transcripts being readable on Windows.
Your 47 readable transcripts and the absence of all 47 IDs in the Ubuntu database give a precise way to check where recovery is possible. On the same Windows package (26.1117.3838.0), my old WSL SQLite index still held the thread IDs, but the Ubuntu connection was using a fresh index.
If you still have a pre-migration index, I'd start by looking for one of the 36 active IDs and one of the 11 archived IDs in a copy of that index. For rows that exist there, check whether their rollout_path resolves to the corresponding transcript on the WSL side. My index recovery script and dry-run instructions report how many paths can be rewritten and how many transcript files would still be missing. The dry-run leaves the destination index uncreated.
There's a separate constraint in your report: my migration stopped before it removed the old project assignments. I could use those mappings to restore the sidebar. Since your migration completed and those mappings are gone from the current state, my result only supports restoring a known thread from a surviving index. Reconstructing which chats belonged to which project would need another source, such as a pre-migration desktop-state backup.
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
rbnrong commentedon Nov 20, 2026
Your 47 readable transcripts and the absence of all 47 IDs in the Ubuntu database give a precise way to check where recovery is possible. On the same Windows package (26.1117.3838.0), my old WSL SQLite index still held the thread IDs, but the Ubuntu connection was using a fresh index.
If you still have a pre-migration index, I'd start by looking for one of the 36 active IDs and one of the 11 archived IDs in a copy of that index. For rows that exist there, check whether their
rollout_pathresolves to the corresponding transcript on the WSL side. My index recovery script and dry-run instructions report how many paths can be rewritten and how many transcript files would still be missing. The dry-run leaves the destination index uncreated.There's a separate constraint in your report: my migration stopped before it removed the old project assignments. I could use those mappings to restore the sidebar. Since your migration completed and those mappings are gone from the current state, my result only supports restoring a known thread from a surviving index. Reconstructing which chats belonged to which project would need another source, such as a pre-migration desktop-state backup.