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

Activity

1. github-actions

   added

   bugSomething isn't workingSomething isn't working

   appIssues related to the Codex desktop appIssues related to the Codex desktop app

   browser

   on Jul 10, 2026
2. github-actions commented on Jul 10, 2026

   

   github-actionsbot

   on Jul 10, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • Codex Desktop renderer crashes after subagent wait with React #185 and unknown conversation state #31090

   Powered by Codex Action
3. brettw-openai commented on Jul 13, 2026

   

   brettw-openai

   on Jul 13, 2026

   More actions

   This should be fixed in the next release.
4. linear

   closed this as completedon Jul 14, 2026
5. constantins2001 commented on Jul 19, 2026

   

   constantins2001

   on Jul 19, 2026 – with ChatGPT Codex Connector

   More actions

   Independent reproduction on a newer macOS build, with a completed large multi-agent task.

   Environment

   • Codex Desktop / ChatGPT app: 26.715.31925 (build 5551)
   • Bundle ID: com.openai.codex
   • macOS 27.0 (build 26A5368g), Apple Silicon / arm64
   • Reproduced 2026-07-19

   Observed trigger

   1. A side chat / execution-side conversation was open.
   2. I selected an older completed local task from the sidebar.
   3. The selected task had a large collaboration history: valid JSONL, about 9.2 MB / 6,259 records, including 242 spawn_agent calls, 542 wait_agent calls, and 356 inter-agent messages.
   4. The main window entered the AppRoutes error boundary with React error #185.

   The transcript itself parses successfully, and the app-server can still read all three completed turns. This does not look like malformed JSONL, native OOM, or a corrupt task.

   Immediately before the error, three different conversation identities were competing in one window:

   • thread_stream_view_activity_changed toggled active=true/false for the previously active side task.
   • browser-sidebar owner sync used a client-new-thread:<uuid> identity.
   • ownerRoutePath pointed to the older task being opened.

   Sanitized excerpt:

   thread_stream_view_activity_changed active=true  conversationId=<side-task>
   thread_stream_view_activity_changed active=false conversationId=<side-task>
   IAB_LIFECYCLE received browser sidebar owner sync
     conversationId=client-new-thread:<uuid>
     ownerRoutePath=/local/<selected-task>
   IAB_LIFECYCLE rebound browser sidebar window
   ...
   error boundary
     errorMessage="Minified React error #185"
     name=AppRoutes
   

   The active/inactive and owner-sync sequence repeated rapidly before the error boundary, matching the loop described in this issue.

   Workaround / additional diagnostic

   Using the native thread/fork operation to make a same-directory copy of the affected task recovered it without modifying the source. The fork contains all original turns and opens successfully in the same worktree. After navigating to the fork, owner sync stabilized on the fork's conversation ID and no React #185 or route reset occurred.

   This suggests the failure is tied to persisted window/sidebar ownership or conversation binding for the original task, rather than its message content alone. Large multi-agent histories may increase the likelihood or timing, but the direct trigger in this reproduction was reopening the task while a side chat remained bound to the window.

   Raw task IDs and full logs are intentionally omitted because the task contains security-review material. I can provide targeted sanitized excerpts if maintainers need more detail.
6. constantins2001 commented on Jul 19, 2026

   

   constantins2001

   on Jul 19, 2026 – with ChatGPT Codex Connector

   More actions

   Follow-up with a narrower and now repeatable trigger: this appears to be a conflict between the Codex Security MCP workspace/sidebar and an ephemeral side chat, not a generic large-thread failure.

   On the recovered parent task, the Codex Security panel cannot be permanently dismissed. When returning from the side chat, the following sequence occurs:

   17:24:38.737 parent task becomes active; sidebar owner sync targets parent
   17:24:38.755 ephemeral side chat becomes active
   17:24:38.784 mcpServer/resource/read succeeds for the parent task
   17:24:38.830 ephemeral side chat becomes inactive
   17:24:38.838 parent sidebar owner sync/rebind repeats
   ...
   17:24:39.757 AppRoutes error boundary: Minified React error #185
   

   For roughly one second, the side chat repeatedly toggles active=true/false while owner sync and sidebar rebind repeatedly target the Codex Security parent route. The component stack includes the shared aside subtree.

   Additional observations:

   • The scan was already complete; this is not an active scan-progress update.
   • The Codex Security resource is re-read when the parent renders, so visually closing/leaving the panel does not dispose its ownership state.
   • The exposed Codex Security MCP surface has open/reopen operations but no close/dispose workspace operation.
   • Archiving the ephemeral side chat does not clear its already-bound renderer state.
   • Forking the parent preserves its historical Security workspace/tool record and remains susceptible.
   • Creating a clean normal project task with the recovered side-chat prompt, without inheriting the Security workspace record, avoids this sidebar collision.

   This suggests the fix should address arbitration/disposal for multiple owners of the shared sidebar/aside surface: a completed Codex Security resource should not continuously reclaim focus, and leaving an ephemeral side chat must unregister its view-activity/ownership bindings before the parent MCP resource rehydrates.