Local environment start button disappeared

Open 💬 3 comments Opened Apr 16, 2026 by waveblink
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

The little start triangle in the top right disappeared from my codex to start my application. Its not a massive deal since I can just start it from the terminal but its still a bit annoying, is there a fix?

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 4 months ago

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

  • #17914
  • #17324
  • #17244

Powered by Codex Action

JustLookAtNow · 2 months ago

I am seeing the same class of issue with local environment actions in Codex App while using a project through a Remote SSH connection into WSL2.

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

Windows Codex Desktop: 26.611.62324

Codex package/CLI version available in the connected WSL2 environment: 0.140.0.

What subscription do you have?

Unknown / not available from this local environment.

What platform is your computer?

Linux 6.6.114.1-microsoft-standard-WSL2 x86_64 x86_64

Codex Desktop is running on Windows and is connected through Remote SSH into this WSL2 environment. The project directory and .codex/environments/environment.toml file are inside WSL2, while the local environment is detected and edited from the Windows Codex Desktop settings panel.

What issue are you seeing?

Local environment actions are configured and visible/editable in the Windows Codex Desktop settings panel, but no action button appears in the Codex Desktop top bar.

I tried restarting the Codex App, but the buttons still do not show up.

The configured local environment file is at the project root:

# THIS IS AUTOGENERATED. DO NOT EDIT MANUALLY
version = 1
name = "flutter_application_m_team"

[setup]
script = ""

[[actions]]
name = "Run Linux"
icon = "run"
command = "env GDK_SCALE=2 GDK_DPI_SCALE=0.875 GTK_IM_MODULE=fcitx QT_IM_MODULE=fcitx XMODIFIERS=@im=fcitx JAVA_HOME=/home/lee/.local/share/mise/installs/java/temurin-17 flutter run -d linux"

[[actions]]
name = "Run Android PKX110"
icon = "run"
command = "flutter run -d PKX110"

The TOML parses successfully, and the Windows Codex Desktop settings panel can see/edit this local environment over the Remote SSH connection. The problem seems specific to rendering/exposing the configured actions in the top bar.

What steps can reproduce the bug?

  1. Connect Codex App to a WSL2 environment through Remote SSH.
  2. Open a project located inside that WSL2 environment in Codex App.
  3. Create .codex/environments/environment.toml in the project root.
  4. Add one or more [[actions]] entries, for example command = "flutter run -d linux".
  5. Open the Windows Codex Desktop settings panel and confirm the local environment is visible/editable there.
  6. Return to the project/thread view.
  7. Observe that no local environment action button appears in the top bar.
  8. Restart Codex App.
  9. Observe that the local environment is still visible/editable in the Windows Codex Desktop settings panel, but the top bar still does not show action buttons.

What is the expected behavior?

Actions defined in .codex/environments/environment.toml should appear in the Codex App top bar and run in the integrated terminal, as described in the Local environments documentation.

Additional information

  • This was reproduced with a Flutter project in a Git repository.
  • The project is accessed through Codex App Remote SSH into WSL2, not as a directly opened local filesystem project.
  • The project root contains the shared .codex folder.
  • The file is ignored by this repository's .gitignore, but is still present in WSL2 and detected by the Windows Codex Desktop settings panel.
Raumo0 · 22 days ago

The same issue on
Version 26.730.61639
Released Aug 5, 2026
macOS Tahoe Version 26.6