›_ Codex Issues
Codex Issues / #18828

Windows Codex app can open repo local environment file in WSL project, but composer dropdown shows "No environments found"

Open 💬 4 comments Opened Apr 21, 2026 by DTadmin-git
💡 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.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
  1. Open the project in the Codex app.
  2. In the composer, open the local environment dropdown.
  3. Observe that it shows:
  • No environment
  • No environments found
  1. Click Create local environment.
  2. Open the same project from the environments page.
  3. Observe that the app successfully opens the existing file:
  • /home/<user>/<repo>/.codex/environments/environment.toml
  1. 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.

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 4 months ago

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

  • #17726

Powered by Codex Action

abdelrahman-mohammad · 4 months ago

Experiencing the same issue!

Neoony · 2 months ago

Same here
Windows 10, running it in WSL
I was trying to migrate my vscode tasks after switching from vscode extension to the app
But the button to run something just does not appear

<img width="374" height="360" alt="Image" src="https://github.com/user-attachments/assets/1ec78cff-4718-4ba6-b481-a9c6228e6ae0" />

<img width="322" height="262" alt="Image" src="https://github.com/user-attachments/assets/2feb3e7f-6ce8-4c3a-bdb9-8e53f166ac9d" />

<img width="770" height="691" alt="Image" src="https://github.com/user-attachments/assets/6ed378d4-fc8e-4aa9-95a4-424a39b8ded0" />

Trying to get these buttons to appear (image from the internet)
<img width="561" height="308" alt="Image" src="https://github.com/user-attachments/assets/f0049d88-bcaf-4259-b5a1-95a742de1c93" />

While I see environments in the codex settings
<img width="840" height="634" alt="Image" src="https://github.com/user-attachments/assets/87b076a0-bd3e-4150-90e4-1cc0571db84f" />

These things keep pushing me back to vscode extension, which works perfectly fine (and vscode has tasks)
I also wish that when I open vscode in codex, it would open it remote from WSL, it seems currently it just opens local one and opens through mnt/
(also have to install and update codex dependencies manually, because it says they are not supported in Windows 10 to be installed through the app...but they work just fine...so far vscode extension is so much less trouble in general, it just works)

<details>
<summary>codex response</summary>

I’m seeing what appears to be the same issue.

Environment:

  • Codex Windows app
  • Project stored in WSL2
  • Repo contains .codex/environments/environment.toml
  • The environment file is readable from Codex environment settings
  • The settings page shows all configured actions correctly

What happens:

  • In the main project/thread UI, the environment dropdown still shows:
  • No environment
  • No environments found
  • Because the environment is not selectable there, the project action/run button does not appear in the top bar.
  • The “Open” dropdown is visible, but the expected actions/play dropdown is missing.

What I verified:

  • .codex/environments/environment.toml exists at the project root.
  • The file follows the documented local environment layout.
  • The repo has a primary Run action plus additional actions.
  • Codex environment settings can load and display the actions.
  • Git tracking/ignore state does not appear to affect this; the file can be tracked, but the composer still does not list the environment.

This looks like the app can read the environment file through settings, but the main composer/project environment selector is not registering WSL-backed repo-local environments.

</details>

zhangyongxianggithub · 1 month ago

Experiencing the same issue!