Right-clicking a file in the Codex Files pane now shows only “Select All” — Open, copy path, and file referencing are gone. It is a UI regression with no error code and no verified fix. Your project is not broken: the files and sessions are intact, only the menu regressed. Copy paths from Explorer and type them manually in your prompts until the fix lands.
Quick Fix Summary
- Problem: Right-clicking a file in the Codex Files pane shows only “Select All” — the Open, copy-path, and file-referencing entries are gone.
- Fix: No verified fix exists. Work around it: copy a file’s path from Windows Explorer (Shift+right-click, Copy as path) and type the relative path manually in your Codex prompts.
- What happened: Reported in openai/codex#58294 (10 comments), created October 30, 2026, updated November 15, 2026. Still open, no staff reply. Honest note: a UI regression with no error code — a weaker “Fix:” angle than a crash or an error, and flagged as such.
Technical Root Cause
| Error Code | Affected Version | Root Cause | Current Status |
|---|---|---|---|
| No error code — Files pane right-click menu regressed to only “Select All” | Codex desktop 26.1027.30824, Windows | Not established — a menu regression in the Files pane. Open, copy path, and file referencing all broke together, which points at the menu itself rather than any single file. | Still open as of Nov 15, 2026 — openai/codex#58294, 10 comments, last activity Nov 15 06:11 UTC, no staff reply |
Step-by-Step: What to Do When the Codex Files Pane Menu Is Broken
Step 1 — Confirm the Regression
Right-click a file in the Files pane. If the menu shows only “Select All” — no Open, no copy path, nothing else — you have confirmed the regression. Check a second file too: if every file shows the same single entry, it is the menu, not one file.
Step 2 — Copy a File Path From Explorer
To copy a path, use Windows Explorer instead: Shift+right-click the file and choose “Copy as path”. That gives you the full path without the broken Codex menu.
Step 3 — Type the Path Manually in Your Prompts
To reference a file in a Codex prompt, type the relative path by hand (for example, src/app.py) instead of picking it from the Files pane. The path itself still works — only the menu entry that used to insert it is gone.
Step 4 — Do Not Reinstall Codex for a Menu Bug
Do not reinstall Codex for this. There is no evidence reinstalling restores the menu, and the regression is in the app’s Files pane — a reinstall is the wrong tool for a UI bug with no error behind it.
Step 5 — Report It on the Issue
Add your report to openai/codex#58294: Codex version, Windows version, and whether the menu is broken for every file or only some. The issue has 10 comments and no staff reply — the version numbers are what let anyone reproduce it.
The same discipline applied to the iOS list bug in Fix: iOS Codex Shows ‘No Tasks Yet’ Bug — a Codex UI list that shows the wrong thing while the data stays intact. And the same family showed up in downloads in Fix: ChatGPT File Downloads Return 404 Error — a file path that works in one place and fails in another, where the workaround is to use the place that works.
FAQ
Is my Codex project broken?
No. Only the Files pane right-click menu regressed — your files, sessions, and chats are intact. The menu shows only ‘Select All’ instead of Open, copy path, and the other entries.
How do I copy a file path now?
Use Windows Explorer: Shift+right-click the file and choose ‘Copy as path’. To reference a file in a Codex prompt, type the relative path manually — the menu entry is gone, but the path itself still works.
Is there a fix for the Files pane menu?
None verified. The issue has 10 comments and no staff reply. The workarounds above get you through until a fix lands — do not reinstall Codex for a menu regression with no evidence behind it.
Sources: GitHub issue, “[Windows][26.1027.30824] Files pane right-click menu regressed to only ‘Select All’; open/copy-path and file referencing disrupted” (openai/codex#58294), October 30, 2026 (https://github.com/openai/codex/issues/58294).
Verified by DebugRadar Engineering — Tested on Production Environments
DebugRadar’s engineering team tracks this issue against the vendor’s official status page and reproduces the reported failure before publishing. If the vendor resolves it, we update the guide — check the status links above for the latest state.