[Desktop] open_in_codex remains queued for the already visible target task

Open 💬 0 comments Opened Aug 21, 2026 by aidawilliam41-ops

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

  1. Start from an existing local report and the currently visible Codex task.
  2. Call open_in_codex for that report and target task.
  3. The operation returns a result equivalent to:
{"status":"queued","threadId":"<current-task>"}
  1. Navigate explicitly to that same task; navigation reports success.
  2. Call open_in_codex again.

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.

View original on GitHub ↗