Possible bug: "Open config.toml in WSL environment" opens Windows config path

Hi,

I tried the new Codex Windows app. I’ve been using Codex CLI from WSL, so I expected my existing configuration to carry over.

In WSL I have a setup with ~/.codex/config.toml, some SKILLS, and several MCP servers defined in the config. In the Windows app, the SKILLS from my WSL ~/.codex directory seem to be detected correctly, but config.toml is not, so my MCP servers are missing.

While checking the Configuration page, I noticed the button “Open config.toml in WSL environment”. When I click it, it opens:

C:\Users\<USER>\.codex\config.toml

instead of the WSL path. So it looks like the button is pointing to the Windows filesystem rather than the WSL config.