[Desktop] open_in_codex remains queued for the already visible target task
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Environment
- Codex Desktop 26.803.5235.0
- Windows
Issue
The Desktop open_in_codex operation does not deliver an existing local report to the right-side panel of the already visible target task.
Reproduction
- Start from an existing local report and the currently visible Codex task.
- Call
open_in_codexfor that report and target task. - The operation returns a result equivalent to:
{"status":"queued","threadId":"<current-task>"}
- Navigate explicitly to that same task; navigation reports success.
- Call
open_in_codexagain.
The second call still returns queued, and the report never appears in the requested panel.
Expected behavior
The visible target task receives the file in its right panel, or the operation returns an actionable terminal error after a bounded timeout.
Actual behavior
The request remains queued with no visible delivery confirmation, queue identifier, failure stage, or way to determine whether it will ever drain.
Impact
A caller can incorrectly tell the user that the report was opened even though nothing is visible. Repeated calls do not recover the operation.
Suggested fix
- Return a stable operation ID and observable queue state.
- Wake or verify the target task's file-panel handler when the task is already visible.
- Add a bounded timeout with the exact delivery stage/error.
- Report success only after the target panel acknowledges the file.
Current workaround: provide a clickable absolute local file link instead of claiming the panel opened.
Task identifiers and the local file path are intentionally omitted. No external data or file contents are included.
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 Desktop open_in_codex operation and the path that returns the queued result, then inspect how the already visible target task handles its file panel. Done means the report is acknowledged by the right-side panel, or the caller receives a stable operation state and bounded, actionable failure instead of an indefinite queued response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100