-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Codex App on Windows, when configured to use WSL, continues to reference the Windows-hosted config.toml #13549
Copy link
Copy link
Open
Labels
appIssues related to the Codex desktop appIssues related to the Codex desktop appbugSomething isn't workingSomething isn't workingterminalIssues related to the in-app terminalIssues related to the in-app terminalwindows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.304.1528.0
What subscription do you have?
Plus for Teams
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
Despite configuring Codex App to use WSL (for both the Agent environment and Integrated terminal shell) and restarting the application, the issue persists. When navigating to Configuration and clicking 'Open config.toml in WSL environment', the app still opens the Windows config.toml instead of the one configured within WSL.
What steps can reproduce the bug?
Steps taken:
- Set Agent environment and Integrated terminal shell to WSL.
- Restarted Codex App.
- Clicked 'Open config.toml in WSL environment' in the Configuration section.
Result: The Windows config.toml opens instead of the WSL-resident file.
What is the expected behavior?
When WSL is selected, the app should point to the config file located at /home/my_user/.codex/config.toml (WSL) instead of C:\Users\my_user\.codex\config.toml (Windows).
Additional information
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
appIssues related to the Codex desktop appIssues related to the Codex desktop appbugSomething isn't workingSomething isn't workingterminalIssues related to the in-app terminalIssues related to the in-app terminalwindows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems