Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Windows Codex app can open repo local environment file in WSL project, but composer dropdown shows "No environments found" [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#18828•Fetched 2026-04-22 07:51:59
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
DTadmin-gitDTadmin-git
Participants
DTadmin-gitDTadmin-gitgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×3commented ×1

Fix Action

Fix / Workaround

Current workaround: No real workaround yet. I can open and edit the environment via the environment editor, but I still cannot select it from the main composer dropdown.

Current workaround: I can open and edit the environment via the environment editor, but I still cannot select it from the main composer dropdown.

RAW_BUFFERClick to expand / collapse

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

26.417.5275.0

What subscription do you have?

Plus

What platform is your computer?

Windows 11, Microsoft Windows NT 10.0.26200.0, x64

What issue are you seeing?

I’m using the Codex Windows app with a project stored in WSL2. The app can open and edit the project local environment file, but the main composer environment selector still shows "No environments found".

Environment:

  • Codex Windows app version: 26.417.5275.0

  • Host OS: Windows 11

  • Runtime: WSL2, Ubuntu

  • Project repo contains:

    • .codex/environments/environment.toml
    • .codex/config.toml

What I expected: The local environment should appear in the composer dropdown and be selectable.

What actually happens:

  • In the main composer, the environment dropdown shows:

    • No environment
    • No environments found

  • But if I click Create local environment and then open the project from the environments page, the app opens the existing file:

    • /home/<user>/<repo>/.codex/environments/environment.toml

  • The environment editor shows the environment name and scripts correctly.

So the app can read the environment file in the editor, but the main composer still does not list it.

Steps to reproduce:

  1. Open a WSL2-backed project in Codex Windows app.
  2. Ensure the repo contains .codex/environments/environment.toml at the project root.
  3. Open the project in the app.
  4. In the composer, open the local environment dropdown.
  5. Observe it says "No environments found".
  6. Click Create local environment.
  7. Open the same project from the environments page.
  8. Observe the app successfully opens and displays the existing environment.toml.

Additional context:

  • WSL2 is confirmed with wsl -l -v.

  • The project is definitely the correct repo.

  • The repo-level .codex/environments/environment.toml exists and is readable by the app.

  • The repo-level .codex/config.toml contains only:

    • sandbox_mode = "workspace-write"

  • I also aligned WSL and Windows Codex home by setting CODEX_HOME to the Windows Codex home directory.

  • That fixed the split Windows vs WSL Codex home issue, but it did not fix the composer dropdown issue.

Current workaround: No real workaround yet. I can open and edit the environment via the environment editor, but I still cannot select it from the main composer dropdown.

What steps can reproduce the bug?

  1. Use the Codex Windows app on Windows 11 with a repo stored in WSL2.

  2. Open a project whose repo contains:

    • .codex/environments/environment.toml
    • .codex/config.toml

  3. Open the project in the Codex app.

  4. In the composer, open the local environment dropdown.

  5. Observe that it shows:

    • No environment
    • No environments found

  6. Click Create local environment.

  7. Open the same project from the environments page.

  8. Observe that the app successfully opens the existing file:

    • /home/<user>/<repo>/.codex/environments/environment.toml

  9. The environment editor shows the environment name and scripts correctly, but the composer dropdown still does not list the environment.

What is the expected behavior?

The local environment defined in .codex/environments/environment.toml should appear in the composer dropdown and be selectable.

If the environment editor can open and read the existing environment file successfully, the composer should also list that environment instead of showing No environments found.

Additional information

Additional context:

  • WSL2 is confirmed with wsl -l -v.
  • The project is definitely the correct repo.
  • The repo-level .codex/environments/environment.toml exists and is readable by the app.
  • The repo-level .codex/config.toml contains only:
    • sandbox_mode = "workspace-write"
  • I also aligned WSL and Windows Codex home by setting CODEX_HOME to the Windows Codex home directory.
  • That fixed the split Windows vs WSL Codex home issue, but it did not fix the composer dropdown issue.

Current workaround: I can open and edit the environment via the environment editor, but I still cannot select it from the main composer dropdown.

extent analysis

TL;DR

The issue might be related to how the Codex app discovers environments in WSL2, and a potential fix could involve ensuring the app correctly scans the WSL2 file system for environment configurations.

Guidance

  1. Verify Environment File Path: Confirm that the .codex/environments/environment.toml file is correctly located and accessible within the WSL2 environment, as the app seems to read it when opening from the environments page.
  2. Check Codex App Configuration: Review the Codex app settings and configuration files (like .codex/config.toml) to ensure there are no settings that might prevent the app from listing environments from WSL2.
  3. Environment Discovery: Investigate if there's an option or setting within the Codex app that controls how environments are discovered, especially in WSL2 contexts, as this might be a point of failure.
  4. WSL2 and Windows Path Alignment: Although setting CODEX_HOME to the Windows Codex home directory fixed the split home issue, double-check that this alignment doesn't inadvertently affect environment discovery in WSL2.

Example

No specific code example is applicable here, as the issue seems related to configuration and environment discovery rather than code implementation.

Notes

The exact solution might depend on specifics of the Codex app's environment discovery mechanism and its interaction with WSL2, which are not fully detailed in the provided information. Further investigation into the app's documentation or support resources may be necessary.

Recommendation

Apply a workaround by manually configuring the environment within the Codex app if possible, or wait for an update that addresses WSL2 environment discovery issues, as the current workaround allows editing but not selecting the environment from the dropdown.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#output truncation#response parsing#generation error#database connection#vector store

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING