[Windows][Codex Desktop 26.721.4979.0] Quick Chat "Open in a new window" closes without showing a new window

Open 💬 2 comments Opened Jul 29, 2026 by DYDgogogo

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

26.721.4979.0

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

The Quick Chat pop-out function is broken in Codex Desktop for Windows.

When I open Quick Chat and click the "Open in a new window" button, the Quick Chat popover immediately disappears, but no new visible ChatGPT window appears. There is no error dialog or other indication that the operation failed.

The issue is consistently reproducible. Fully quitting and reopening Codex Desktop does not resolve it, and restarting Windows does not resolve it.

Opening another complete Codex Desktop window is not an equivalent workaround. The intended workflow is to have the main Codex Desktop window on one side of the screen and a lightweight, independent ordinary ChatGPT Quick Chat window on the other side.

What steps can reproduce the bug?

Feedback ID: no-active-thread-019facf7-f815-7810-9f7d-2a24c5872841

What is the expected behavior?

Clicking "Open in a new window" should move Quick Chat into a separate, visible, resizable ChatGPT window.

The original Quick Chat popover should close only after the new window has loaded successfully.

The new window should host the lightweight ordinary ChatGPT Chat experience. It should not open another complete Codex Desktop window.

This should allow a dual-window workflow with Codex Desktop on one side of the screen and ordinary ChatGPT Quick Chat on the other side.

Additional information

Environment

Codex Desktop version: 26.721.4979.0
Package: OpenAI.Codex_26.721.4979.0_x64__2p2nqsd0c76g0
Operating system: Windows 10 Pro, 64-bit, build 19045
Subscription: ChatGPT Pro
Device: Lenovo ThinkPad

Troubleshooting already performed

Fully quit and relaunched Codex Desktop.
Restarted Windows.
Repeated the operation multiple times.
Confirmed that ordinary ChatGPT works normally through the PWA.
Confirmed that opening a second complete Codex window is not an equivalent replacement for the Quick Chat pop-out.

Local diagnostic evidence

Local diagnostics indicate that the button click is registered successfully.

A hidden auxiliary ChatGPT window matching the expected pop-out size was observed at an on-screen position. This makes an off-screen window-placement problem unlikely.

The auxiliary renderer also recorded this warning:

Matched leaf route at location "/" does not have an element or Component. This means it will render an <Outlet /> with a null value by default resulting in an "empty" page.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#35121
#34906

Powered by Codex Action

aidawilliam41-ops · 7 days ago

Source- and log-level evidence from the affected Windows build

Additional evidence from Codex Desktop 26.721.4979.0 supports the reported silent-failure path.

The shipped Quick Chat renderer action quickChat.popOut is presented as Open in a new window. In the packaged renderer implementation, the action calls quickChatWindow.open(...) without awaiting or catching a success/failure result and immediately dismisses the floating Quick Chat.

The main-process implementation keeps the new Quick Chat window hidden until a route-ready handshake completes. If that handshake or its timeout path fails, the function returns without showing the window and without surfacing an actionable error to the caller.

Sanitized current-session evidence from the affected build:

Quick Chat windows 3, 4, 5, 6, and 7 loaded with rendererWindowVisible=false.
Across 53 Quick Chat renderer log lines, visible=true occurred zero times.
One hidden window also recorded a post-login bootstrap timeout.
The owner-visible result matched this state: the source popover disappeared, but no separate visible Quick Chat window appeared.

This suggests that hidden window creation/prewarming can succeed far enough to dismiss the source while visible readiness never completes.

Suggested correction:

Await quickChatWindow.open() and return an explicit success/failure result.
Dismiss the source Quick Chat only after the destination window is visibly ready.
Retain the source and show a retryable error on failure.
Log the exact failed stage: creation, navigation, route readiness, renderer readiness, or display.

This evidence is version-scoped to 26.721.4979.0. I did not re-exercise the state-changing pop-out action solely to reproduce it on the current build, so no claim is made here about newer versions. No account identifiers, task content, local paths, or raw logs are included.