Skip to content

[Windows][WSL] Automatic migration leaves projects with no chats despite intact Windows history #62735

Open

Description

@Av1dity

Environment

  • Codex Windows package 26.1117.3838.0
  • Ubuntu via WSL
  • Observed on November 20, 2026

Steps to reproduce

  1. Use the Windows desktop app with the legacy WSL agent environment and existing project chats.
  2. Update and relaunch on an installation that receives the automatic migration to WSL remote connections.
  3. 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.

Activity

  1. added
    bugSomething isn't working
    appIssues related to the Codex desktop app
    windows-osIssues related to Codex on Windows systems
    sessionIssues involving session (thread) management, resuming, forking, naming, archiving
    on Nov 20, 2026
  2. github-actions commented on Nov 20, 2026

    @github-actions
    Contributor

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

    Powered by Codex Action

  3. rbnrong commented on Nov 20, 2026

    @rbnrong

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingremotesessionIssues involving session (thread) management, resuming, forking, naming, archivingwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions