[Windows][WSL] Switching Agent Environment from Windows Native to WSL hides existing project sessions
What version of the Codex App are you using (From “About Codex” dialog)?
26.803.81509
What subscription do you have?
ChatGPT Pro
What platform is your computer?
Windows 11 x64, WSL2 with Ubuntu
What issue are you seeing?
When I switch Codex App Settings → Agent Environment from Windows Native to Windows Subsystem for Linux (WSL), some existing sessions under my projects are no longer visible.
The sessions do not appear to be deleted. Pinned sessions remain visible, while some non-pinned sessions disappear.
If I pin an affected session, it becomes visible again.
I first noticed this issue about 2–3 weeks ago, and it is still present in Codex App 26.803.81509.
What steps can reproduce the bug?
- Open Codex App on Windows.
- Set Settings → Agent Environment to Windows Native.
- Open a project that already contains multiple sessions.
- Confirm that the sessions are visible.
- Pin one or more sessions for comparison.
- Change Settings → Agent Environment to Windows Subsystem for Linux (WSL).
- Open the same project again.
- Some previously visible non-pinned sessions are no longer shown, while pinned sessions remain visible.
- Pinning an affected session makes it visible again.
What is the expected behavior?
Changing the Agent Environment should change where the agent executes commands, but existing project sessions and conversation history should remain visible.
Existing sessions should remain accessible regardless of whether they were originally created using Windows Native or WSL.
Additional information
_No response_
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Thanks. #37768 looks related, especially the sidebar behavior and the fact that pinning makes hidden sessions visible.
However, my reproduction is different: I can trigger the issue specifically by switching Settings → Agent Environment from Windows Native to WSL. I have not observed config.toml truncation in my case.
This may share the same sidebar/session indexing issue, possibly around Windows/WSL project path mapping.