Codex Desktop 26.707: opening side dialog triggers browser-sidebar rebind loop and React #185 error boundary

Resolved 💬 4 comments Opened Jul 10, 2026 by robin-byte Closed Jul 14, 2026

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

  • Codex Desktop / ChatGPT app: 26.707.31428
  • Build: 5059
  • Bundle ID: com.openai.codex
  • Bundled Chromium framework: 150.0.7871.101

What subscription do you have?

ChatGPT subscription with Codex access (exact plan not provided).

What platform is your computer?

  • macOS 26.5.1 (25F80)
  • Apple Silicon, arm64
  • UI language: Simplified Chinese

What issue are you seeing?

Clicking the execution-side / side-conversation dialog in a Codex task causes the entire main window to enter the app-wide error fallback.

The visible message is:

  • 糟糕,出错了 ("Something went wrong")
  • Buttons: 更新 ChatGPT ("Update ChatGPT") and 重试 ("Try again")

No error code or diagnostic details are shown in the UI. The installed app is already current, so the update action does not explain the failure.

The local desktop log identifies an AppRoutes renderer error boundary with:

Minified React error #185

Immediately before the error, the log enters a rapid state-update loop involving:

  • thread_stream_view_activity_changed: 57 events
  • IAB_LIFECYCLE received browser sidebar owner sync: 58 events
  • IAB_LIFECYCLE rebound browser sidebar window: 58 events

These events occur within roughly four seconds. The active thread repeatedly toggles between active=true and active=false, while the browser sidebar is rebound to the same owner window.

Sanitized excerpt:

2026-07-10T12:18:45.xxxZ IAB_LIFECYCLE received browser sidebar owner sync browserTabId=null ...
2026-07-10T12:18:45.xxxZ IAB_LIFECYCLE rebound browser sidebar window ownerWebContentsId=1 previousOwnerWebContentsId=1 windowId=1
2026-07-10T12:18:45.xxxZ thread_stream_view_activity_changed active=true ... resumeState=resumed streamRole=owner
2026-07-10T12:18:45.xxxZ thread_stream_view_activity_changed active=false ... resumeState=resumed streamRole=owner
2026-07-10T12:18:46.103Z error ... errorMessage="Minified React error #185" name=AppRoutes
2026-07-10T12:18:46.124Z warning [IpcClient] Received broadcast but no handler is configured method=ipc-connection-reset

No macOS .ips crash report was generated, so this appears to be a renderer/state-update failure rather than a native process crash.

A screenshot was captured at the time of failure. It shows the full-screen fallback and the two buttons above, with no additional diagnostic information.

What steps can reproduce the bug?

  1. Open Codex Desktop on macOS and enter a local Codex task.
  2. Click the execution-side / side-conversation dialog or panel.
  3. Observe the main window.

Observed on July 10, 2026 at 20:18:46 (Asia/Shanghai, UTC+8).

What is the expected behavior?

The side dialog should open and render normally.

If the dialog cannot load, the failure should remain scoped to that panel and provide a useful diagnostic or recovery action. It should not trigger an unbounded sidebar/view-activity update loop or replace the entire app with the generic error boundary.

Additional information

  • The component stack includes local-conversation-thread, quick-chat-window-page, and an aside subtree before the AppRoutes boundary.
  • Full raw logs were not attached because they contain task metadata. Sanitized excerpts can be provided if needed.
  • Possibly related: openai/codex#31090 also reports a full-screen Codex Desktop fallback with React [#185](<https://github.com/openai/codex/issues/185>), but its observed trigger is subagent/session-state handling rather than opening the side dialog and entering a browser-sidebar rebind loop.

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗