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 desktop blocks remote WSL migration with ChatGPT-linked projects and shows a misleading install warning #62686
With legacy WSL enabled and two ChatGPT-linked local projects present, restarting the app showed “This installation cannot switch yet.” The dialog only offered “Keep legacy WSL mode.” The app then showed a warning instructing me to install WSL and the Codex CLI. Ubuntu was unavailable in Connections while migration was blocked.
Diagnostics
wsl -d Ubuntu --exec codex --version returned codex-cli 0.171.0.
The desktop migration logs showed linkedProjectCount=2, syncedAutomations=false, reason=unsupported_data, and stage=blocked.
On a later restart, the logs showed linkedProjectCount=0 and stage=completed. The desktop then reported remote-wsl:Ubuntu as connected. This verifies the connection after migration. A new desktop chat on that connection was not independently verified.
Expected behavior
Allow the Ubuntu connection to be enabled while preserving linked projects and their chats. If migration must be blocked, show the linked-project limitation in the warning and explain the available options.
I hit the same reason=unsupported_data with two ChatGPT-linked projects on Windows desktop 26.1117.31558. One detail that might help distinguish the warning from a WSL installation problem: on my machine the “This installation cannot switch yet” prompt still appears, even though I can open an old chat on the Ubuntu connection, send a new turn there, and resume it from the bundled WSL CLI (0.171.0-alpha.13).
I recovered the old chats separately. The Windows host had indexed the legacy transcripts, while the new Ubuntu connection had started with an empty history. Pointing the WSL host at a copy of the old index and restoring its project assignments brought back 13 remote projects. This didn't require deleting the ChatGPT-linked projects or installing a second CLI.
I've documented the versions, recovery steps and remaining migration prompt. For the warning itself, showing the existing linkedProjectCount and whether the runtime is already reachable would have saved me from troubleshooting the wrong thing.
Activity
rbnrong commentedon Nov 20, 2026
I hit the same
reason=unsupported_datawith two ChatGPT-linked projects on Windows desktop 26.1117.31558. One detail that might help distinguish the warning from a WSL installation problem: on my machine the “This installation cannot switch yet” prompt still appears, even though I can open an old chat on the Ubuntu connection, send a new turn there, and resume it from the bundled WSL CLI (0.171.0-alpha.13).I recovered the old chats separately. The Windows host had indexed the legacy transcripts, while the new Ubuntu connection had started with an empty history. Pointing the WSL host at a copy of the old index and restoring its project assignments brought back 13 remote projects. This didn't require deleting the ChatGPT-linked projects or installing a second CLI.
I've documented the versions, recovery steps and remaining migration prompt. For the warning itself, showing the existing
linkedProjectCountand whether the runtime is already reachable would have saved me from troubleshooting the wrong thing.