Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Codex Desktop reconnect loop on new/restarted conversations due to turn/started for unknown conversation [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#21167•Fetched 2026-05-06 06:25:29
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
qinggang626543qinggang626543
Participants
github-actions[bot]github-actions[bot]qinggang626543qinggang626543
Timeline (top)
labeled ×4cross-referenced ×2commented ×1

Codex Desktop consistently enters a reconnect loop when I:

  • start a new conversation
  • restart an old conversation

This is reproducible on every attempt in the desktop app.

The issue does not appear to be caused by my VPN or local cache state. I reset the relevant local storage areas and the behavior remained unchanged.

Root Cause

The issue does not appear to be caused by my VPN or local cache state. I reset the relevant local storage areas and the behavior remained unchanged.

RAW_BUFFERClick to expand / collapse

Summary

Codex Desktop consistently enters a reconnect loop when I:

  • start a new conversation
  • restart an old conversation

This is reproducible on every attempt in the desktop app.

The issue does not appear to be caused by my VPN or local cache state. I reset the relevant local storage areas and the behavior remained unchanged.

Environment

  • Product: Codex Desktop
  • Date observed: May 5, 2026
  • OS: macOS
  • App version seen in session metadata: 0.128.0-alpha.1

Reproduction

  1. Open Codex Desktop
  2. Start a new conversation
  3. Or restart an old conversation
  4. Observe repeated Reconnecting... retries
  5. Eventually it may recover, but the reconnect loop happens first

Expected behavior

New conversations and restarted conversations should start normally without reconnect loops.

Actual behavior

The app shows repeated reconnect attempts specifically at conversation start / restart time.

Key log evidence

In the desktop logs, the pattern is:

  1. browser sidebar thread is registered with conversationId=new-conversation
  2. browser-use is force-installed at runtime
  3. the conversation is created successfully
  4. turn/start is routed successfully for the expected conversation
  5. immediately after that, the app logs:

Received turn/started for unknown conversation

This strongly suggests a conversation routing bug inside the desktop app.

Example reproduction after local reset

Log file:

/Users/qinggang/Library/Logs/com.openai.codex/2026/05/05/codex-desktop-cc899bf8-644a-44ab-8b1f-e69327433dde-53115-t0-i1-101625-0.log

Relevant sequence from that log:

  • registered browser sidebar thread conversationId=new-conversation
  • forceInstallPluginNames=["browser-use"]
  • bundled_plugin_install_requested pluginName=browser-use reason=forced
  • Conversation created conversationId=019df7a3-a20a-7671-8c71-af4fafb29e9c
  • normal turn/start
  • captured turn route conversationId=019df7a3-a20a-7671-8c71-af4fafb29e9c
  • then: Received turn/started for unknown conversation conversationId=019df7a3-b244-7f80-8d4d-5de2d6ed71b1

Earlier matching reproductions

Same pattern was also seen for these conversations:

  • 019df631-720c-7ba3-9a40-0849d27bbd9b
  • 019df78a-be9e-7e12-8125-5788c03e7a9b

What I already tried

I ruled out local state corruption by resetting these areas:

  • main app Session Storage
  • main app SharedStorage
  • browser partition Partitions/codex-browser-app

I also set this in ~/.codex/config.toml:

[plugins."browser-use@openai-bundled"]
enabled = false

[codex-desktop-reconnect-findings-2026-05-05.md](https://github.com/user-attachments/files/27395651/codex-desktop-reconnect-findings-2026-05-05.md)

extent analysis

TL;DR

The issue is likely caused by a conversation routing bug inside the Codex Desktop app, resulting in a reconnect loop when starting or restarting conversations.

Guidance

  • Review the conversation routing logic in the Codex Desktop app to ensure that conversation IDs are being handled correctly.
  • Verify that the turn/start route is being sent with the correct conversation ID.
  • Check the app's logging mechanism to see if there are any errors or warnings related to conversation ID handling.
  • Consider temporarily disabling the browser-use plugin to see if it resolves the issue.

Example

No code snippet is provided as the issue is related to the app's internal logic and not a specific code block.

Notes

The issue seems to be specific to the Codex Desktop app and not related to local state corruption or VPN issues. The provided log evidence suggests a conversation routing bug, but further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Disable the browser-use plugin temporarily to see if it resolves the issue, as it is force-installed at runtime and may be contributing to the reconnect loop.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

New conversations and restarted conversations should start normally without reconnect loops.

#inference speed#output truncation#response parsing#generation error#database connection

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING