[Windows][26.831.2377.0] Right-panel file and browser tabs stay queued and render blank
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.831.2377.0
What subscription do you have?
Pro20
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
On Windows, the Codex App creates a tab header, but the tab content does not appear in the right panel.
The open_in_codex action returns a queued status even while the target thread is visible. The application log repeatedly records:
Failed to run queued app action error={}
The problem reproduces with:
- a valid local PDF,
- a valid PNG copied to a short local path,
- an HTTPS browser URL.
The files open correctly outside Codex. This is not limited to one file type or to long paths.
What steps can reproduce the bug?
- Open an existing local Codex task on Windows.
- Ask Codex to open a valid local PDF in the right panel.
- Observe that the tab header appears, but the content is blank and the action reports
status: queued. - Repeat with a valid PNG stored at a short local path.
- Repeat with a normal HTTPS browser URL.
- Navigate explicitly back to the current task and retry.
- Fully restart Codex and retry.
- Update from 26.825.6671.0 to 26.831.2377.0, restart, and retry.
- Fork the task into a new same-directory task and retry.
Result: every attempt remains queued. The same log warning is recorded for both the original task and the fork.
What is the expected behavior?
The selected local file or HTTPS page should open immediately in the visible right panel. If opening fails, the app should show an actionable error instead of creating a blank tab and leaving the action queued.
Additional information
The issue persists after a full application restart and after updating to 26.831.2377.0.
It reproduces in both the original task and a newly created same-directory fork, so it does not appear to be limited to one thread.
Potentially related to #29078, but this case differs: it occurs on Windows, in a current task, across local PDF/PNG files and HTTPS browser tabs, and includes a repeated queued-action failure in the app log.
Full logs are not attached because they contain private local workspace paths. Redacted excerpts can be provided if needed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the open_in_codex app action and the repeated “Failed to run queued app action” log on Windows, reproducing it with a local PDF, PNG, and HTTPS URL. Done means the selected content renders in the visible right panel, or a clear actionable error is shown instead of a blank queued tab.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100