Windows App: Not picking WSL thread history

Open 💬 7 comments Opened Mar 6, 2026 by zg-alexey

💡 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)?

There is no About Codex on Windows - separate bug :)

What subscription do you have?

Plus

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

I have Codex app set to WSL agent and shell.
I add project inside WSL - app is not picking thread history I already have there in CLI Codex/Cursor/VSCode plugin.

What steps can reproduce the bug?

Set app to use WSL in agent and shell. Restart it. Add project from inside WSL (on WSL drive) - any repo which has a number of threads created through CLI Codex or Cursor/VSCode plugin.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

7 Comments

github-actions[bot] contributor · 4 months ago

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

#13713
#13762
#13549

Powered by Codex Action

shurkanTwo · 4 months ago

I have the same issue.

Jen1us · 3 months ago

same issue

shurkanTwo · 3 months ago

any update on this?
I am really eager to start using the Codex App. but until this is fixed I will continue to use the VS Code extension...

yguedidi · 3 months ago

Said differently it would be great that when the app is configured to use WSL, it acts like a nice easy to use UI for the codex CLI inside WSL

ntaylor-ads · 3 months ago

same issue. Better WSL support would be much appreciated

curserio · 2 months ago

I did a bit of local digging on a Windows + WSL setup and found one thing that may be relevant.

Environment:

Codex Windows App: 26.422.2437.0
WSL CLI used by the app: codex-cli 0.124.0-alpha.2
Windows: 10.0.26200.8246
WSL: Ubuntu 24.04, WSL2
Repo is on the WSL filesystem: /home/<user>/.../<repo>

What I see locally:

WSL Codex home: /home/<user>/.codex
has 19 rollout JSONL files under sessions
state_5.sqlite has 22 thread rows
these are mostly from VS Code / CLI inside WSL

Windows Codex home: /mnt/c/Users/<user>/.codex
has only 3 rollout JSONL files under sessions
state_5.sqlite has 0 thread rows

The interesting part: the WSL-created sessions and the Desktop-created sessions for this repo both store the cwd as a WSL path like:

/home/<user>/.../<repo>

So at least in my case this does not look primarily like a cwd mismatch. It looks more like the Windows App is reading/indexing the Windows-side Codex home, while CLI / VS Code inside WSL are writing to the WSL-side Codex home.

Possible fix direction:

When the Windows App is using a WSL agent/shell, it may need to read/index the selected distro’s $HOME/.codex as the primary Codex home, or merge it with the Windows-side Codex home. It would also help to have a small diagnostic showing which Codex home the app is currently using for thread history.