Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Bug report: Codex Desktop hides Open / quick actions in non-Git workspaces [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#17726•Fetched 2026-04-14 05:41:07
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
AdrianPonceDRAdrianPonceDR
Participants
AdrianPonceDRAdrianPonceDRgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×2commented ×1
RAW_BUFFERClick to expand / collapse

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

41.2.0

What subscription do you have?

Plus

What platform is your computer?

Windos

What issue are you seeing?

Hello,

I would like to report what appears to be a regression in Codex Desktop on Windows.

In Codex Desktop 41.2.0, several workspace controls disappeared for one of my local projects while the folder was not a Git repository. The missing controls included:

  • the “Open” button
  • the quick action / quick command dropdown
  • Git-related workspace controls

At first I suspected a broken local project configuration, but that does not seem to be the case. The workspace was still trusted, local actions were still defined in .codex/environments/environment.toml, Codex still remembered the folder as the active workspace, and I did not find parse errors in the logs.

I then tested the same folder by running git init and reopening the workspace in Codex. Immediately after that, the missing controls reappeared, including:

  • the “Open” button
  • the quick action dropdown
  • Git workspace indicators/controls

This strongly suggests that these UI controls are currently being gated by Git workspace detection. In practice, when the folder is not recognized as a Git workspace, the entire control block appears to be hidden.

Why this seems incorrect: At least some of these controls, especially “Open” and configured local quick actions, are still relevant for trusted local workspaces even when the folder is not a Git repository. Git-specific controls being disabled would make sense, but hiding the whole workspace action area does not.

What steps can reproduce the bug?

  1. Open a trusted local workspace that is not a Git repository.
  2. Ensure .codex/environments/environment.toml exists and defines valid local actions.
  3. Open the workspace in Codex Desktop 41.2.0.
  4. Observe that “Open”, quick actions, and Git-related controls are missing.
  5. Run git init in the same folder.
  6. Reopen the same workspace in Codex.
  7. Observe that the missing controls reappear.

What is the expected behavior?

  • “Open” and configured local quick actions should remain available in trusted local workspaces, even if the folder is not a Git repository.
  • Git-specific controls may be disabled, hidden, or replaced with an “Initialize Git” action, but the whole control area should not disappear.

Actual behavior:

  • the full action/control block appears to be hidden when the workspace is not detected as Git
  • the same controls reappear immediately after git init

This looks like a UI regression or an overly strict condition tied to Git workspace classification.

Additional information

No response

extent analysis

TL;DR

The issue can be worked around by initializing a Git repository in the local workspace folder using git init, which will cause the missing controls to reappear in Codex Desktop 41.2.0.

Guidance

  • Verify that the workspace is trusted and local actions are defined in .codex/environments/environment.toml to ensure the issue is not related to project configuration.
  • Run git init in the workspace folder to initialize a Git repository, which should cause the missing controls to reappear.
  • Test the workspace controls after initializing the Git repository to confirm the workaround is effective.
  • Consider reporting this issue to the Codex App developers, as the expected behavior is for certain controls (e.g., "Open" and local quick actions) to remain available even when the folder is not a Git repository.

Example

No code snippet is necessary for this issue, as the workaround involves running a Git command (git init) rather than modifying code.

Notes

This workaround may not be ideal, as it requires initializing a Git repository in a folder that may not need version control. The underlying issue appears to be a UI regression or overly strict condition tied to Git workspace classification, which should be addressed by the Codex App developers.

Recommendation

Apply the workaround by running git init in the workspace folder, as this will allow access to the missing controls until a fix is available from the Codex App developers.

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…
#cache error#pipeline error#runtime error#dependency conflict#environment setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING