Resume a previous session not working on WSL Ubuntu
Resolved 💬 4 comments Opened Nov 19, 2025 by PrzemyslawKlys Closed Nov 20, 2025
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
codex-cli 0.59.0
What subscription do you have?
Pro
Which model were you using?
gpt-5.1-codex-max high
What platform is your computer?
x64
What issue are you seeing?
Hi,
Just updated to newest version on ubuntu WSL:
<img width="1565" height="1969" alt="Image" src="https://github.com/user-attachments/assets/21783fbc-42e3-44aa-a8c5-b1d0eb424572" />
No sessions are loading.
On Windows (which I guess doesn't share the same sessions it loads
<img width="768" height="554" alt="Image" src="https://github.com/user-attachments/assets/05437e09-e3bc-480a-ac59-64cec882e7d3" />
But the WSL one has a lot of older sessions going back months
What steps can reproduce the bug?
- Start codex
codex resume --enable web_search_request --dangerously-bypass-approvals-and-sandboxon WSL - See the issue
What is the expected behavior?
Loading same as on Windows
Additional information
_No response_
4 Comments
The latest version of the Codex CLI introduced a change to
codex resumethat filters the list of resumable sessions based on the current working directory. If you runcodex resume --all, you should see all of your sessions even if they don't match your cwd. Does that explain the behavior you're seeing?No, it wasn't working. I was in correct directory. However updating to new version 0.60.1 fixed it. Could have been a hiccup and just required reboot or something. Thank you!
@etraut-openai I guess what would be cool if Windows version and WSL version would use the same sessions storage, and be able to continue. I have Windows based project so they don't run in WSL and yet I prefer WSL for it's coding capabilities with Codex. Would be nice to just continue session on Windows for troubleshooting.
Sharing between Windows and WSL is effectively the same problem as sharing between two codex installations on different computers despite Windows and WSL being hosted on the same physical machine. The installation config and sessions are distinct because of this. If we made WSL and Windows share config and sessions, then we'd run into problems with versioning, locking, etc. Not insurmountable, but definitely a non-trivial amount of complexity to do right. The better way to handle this is making sessions portable between installations (cli -> cli -> cloud etc.) rather than shared. I think there's probably some issues that track this work, but my search-fu is not the best today.