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
Existing chats cannot migrate from deprecated legacy WSL project to newly added WSL project #61598
After Codex Desktop for Windows auto-updated, the previous global/legacy WSL agent environment was replaced by the new project-connected WSL flow. Existing chats remain attached to the deprecated WSL project and cannot be continued or moved to the newly added WSL project, even when it points to the exact same repository.
The Settings UI shows a warning equivalent to:
The legacy WSL agent environment has been deprecated. Visit a project connected with WSL, or add a new project.
After restart, the agent environment returns to Windows Native. Adding the same repository again through \\wsl$\<distro>\path\to\repo creates a new project identity, while the old chats continue reporting that the original project cannot be found.
Steps to reproduce
Have existing Codex Desktop chats associated with a repository using the former WSL agent environment.
Allow Codex Desktop for Windows to auto-update to the version that deprecates the legacy WSL agent environment.
Open an old chat: it reports that the original project cannot be found.
Add the same repository again using the WSL filesystem picker.
Try to continue or migrate the old chat into the newly added WSL project.
Try /resume with scope All and /fork.
Actual behavior
The newly added WSL project works as a separate project.
Existing chats remain bound to the deprecated project identity.
The old chats cannot be rebound, resumed into, forked into, or transferred to the new WSL project.
Restarting the app does not repair the association.
Expected behavior
When the same WSL distribution and repository path are added after migration, Codex Desktop should either:
automatically reconnect existing chats to the new WSL project identity; or
provide a user-facing “Rebind/migrate chats to project” action, ideally supporting bulk migration.
The original threads and their history should remain intact.
I ran into the two-project-identities case on Windows desktop 26.1117.31558. The legacy local project still had a \\wsl$\Ubuntu\… root. The new remote project had the same Linux directory, a remote-wsl:Ubuntu host, and a different project ID. The saved thread assignments still named the old ID. That gave me a way to identify which chats belonged together without guessing from their titles.
With a backup of the original desktop state, I matched projects by WSL distribution and Linux path, then repointed 120 existing assignments from the old local projects. Two more needed a separate correction. I've published the two sidebar scripts and their dry-run commands. They preview which projects match and how many assignments would move. That preview depends on the old assignments still being present; it can't reconstruct ones that have already disappeared.
This is why the bulk Rebind chats action you describe would have helped in my case: Desktop already had both project identities and enough information to preview the matches before asking the user to confirm.
Activity
rbnrong commentedon Nov 20, 2026
I ran into the two-project-identities case on Windows desktop 26.1117.31558. The legacy local project still had a
\\wsl$\Ubuntu\…root. The new remote project had the same Linux directory, aremote-wsl:Ubuntuhost, and a different project ID. The saved thread assignments still named the old ID. That gave me a way to identify which chats belonged together without guessing from their titles.With a backup of the original desktop state, I matched projects by WSL distribution and Linux path, then repointed 120 existing assignments from the old local projects. Two more needed a separate correction. I've published the two sidebar scripts and their dry-run commands. They preview which projects match and how many assignments would move. That preview depends on the old assignments still being present; it can't reconstruct ones that have already disappeared.
This is why the bulk Rebind chats action you describe would have helped in my case: Desktop already had both project identities and enough information to preview the matches before asking the user to confirm.