Codex Windows App in WSL mode chats are not resumable in WSL TUI

Resolved 💬 5 comments Opened Jun 2, 2026 by kendonB Closed Aug 4, 2026

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

26.527.60818 Beta

What subscription do you have?

Pro

What platform is your computer?

Windows 11 x64

What issue are you seeing?

codex resume in the same folder should show the chats from the app and it doesn't.

What steps can reproduce the bug?

Run a chat in the app, codex resume in the same folder in the TUI

What is the expected behavior?

App chat is there

Additional information

_No response_

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 2 months ago

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

#24364

Powered by Codex Action

kendonB · 2 months ago

Copying session id doesn't work

kendonb@kendonb:~/projects/climate-data-wells$ codex resume 019e7651-2fef-7d12-8a79-4bd6803eaaf3
ERROR: No saved session found with ID 019e7651-2fef-7d12-8a79-4bd6803eaaf3. Run `codex resume` without an ID to choose from existing sessions.
kendonb@kendonb:~/projects/climate-data-wells$

kendonB · 2 months ago

Is this as simple as setting CODEX_HOME inside the app to ~/.codex/ instead of /mnt/c/Users/USERNAME/.codex? This is clearly the right default in WSL mode.

Necmttn · 2 months ago

This sounds like a storage-root identity problem.

The app and WSL TUI need to agree on Codex home, project cwd normalization, and session source root. A diagnostic row in the resume picker could show session_id, source root, cwd as stored, current cwd, and whether the active CODEX_HOME can see that JSONL/index entry.

Then users see wrong root instead of No saved session found.

---

_Generated with ax._

kendonB · 23 days ago

fixed