codex - 💡(How to fix) Fix Codex Desktop on macOS was very slow today and kept reconnecting to the local app-server [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#19109Fetched 2026-04-24 06:00:47
View on GitHub
Comments
1
Participants
2
Timeline
8
Reactions
0
Timeline (top)
labeled ×4closed ×1commented ×1cross-referenced ×1

Today Codex Desktop was very slow to use on macOS, and it also kept reconnecting to the local app-server.

The core problem I want to report is not just "general performance feels bad". The main symptom today was:

  1. access/use felt slow
  2. the desktop app repeatedly reconnected

I originally filed this too broadly, so this updated report is specifically about slow access together with repeated reconnect behavior.

Error Message

One stop event included this error context: error [electron-message-handler] Received turn/started for unknown conversation conversationId=...

Root Cause

Today Codex Desktop was very slow to use on macOS, and it also kept reconnecting to the local app-server.

The core problem I want to report is not just "general performance feels bad". The main symptom today was:

  1. access/use felt slow
  2. the desktop app repeatedly reconnected

I originally filed this too broadly, so this updated report is specifically about slow access together with repeated reconnect behavior.

Code Example

info [AppServerConnection] app_server_connection.state_changed cause=start_process ... next=connecting ... transport=stdio

---

info [AppServerConnection] app_server_connection.state_changed cause=stop_process ... next=disconnected ... transport=stdio

---

failed to refresh available models: timeout waiting for child process to exit

---

failed to warm featured plugin ids cache ... 401 Unauthorized

---

error [electron-message-handler] Received turn/started for unknown conversation conversationId=...
RAW_BUFFERClick to expand / collapse

Summary

Today Codex Desktop was very slow to use on macOS, and it also kept reconnecting to the local app-server.

The core problem I want to report is not just "general performance feels bad". The main symptom today was:

  1. access/use felt slow
  2. the desktop app repeatedly reconnected

I originally filed this too broadly, so this updated report is specifically about slow access together with repeated reconnect behavior.

Environment

  • Codex Desktop
  • macOS 15.7.4
  • App-server version seen repeatedly in today's logs: 0.122.0-alpha.13
  • Runtime bundle: 26.416.11627

What I observed

  • Codex felt slow throughout today
  • While using it, the app repeatedly appeared to disconnect and reconnect
  • The issue felt like connection churn, not just a heavy thread rendering slowly once

Expected behavior

  • Codex Desktop should stay responsive during normal use
  • The local app-server connection should remain stable instead of repeatedly reconnecting

Actual behavior

  • Access/use was slow today
  • The app repeatedly went through reconnect-like connection cycles

Local evidence from today

For 2026-04-23:

  • 29 codex-desktop-*.log files were generated
  • Today's logs contain about 15 cause=start_process state transitions
  • Today's logs contain about 15 cause=stop_process state transitions
  • ~/.codex/logs_2.sqlite is about 753 MB
  • ~/.codex/logs_2.sqlite currently contains about 151,652 log rows

Other signals that showed up while this was happening:

  • Received turn/started for unknown conversation: about 159 occurrences
  • Not a git repository: about 6,718 occurrences
  • unsupported feature enablement 'realtime_conversation': about 138 occurrences
  • 401 Unauthorized: about 2 occurrences

Example log snippets

Repeated connection start:

info [AppServerConnection] app_server_connection.state_changed cause=start_process ... next=connecting ... transport=stdio

Repeated connection stop:

info [AppServerConnection] app_server_connection.state_changed cause=stop_process ... next=disconnected ... transport=stdio

One stop event included this error context:

failed to refresh available models: timeout waiting for child process to exit

Another stop event included:

failed to warm featured plugin ids cache ... 401 Unauthorized

I also saw:

error [electron-message-handler] Received turn/started for unknown conversation conversationId=...

Notes

  • The main reason I am filing this is the combination of slow access plus repeated reconnect behavior
  • The extra log noise above may or may not be causal, but it was present during the same time window
  • If useful, I can provide a narrower time window or more exact raw log excerpts around a reconnect event

extent analysis

TL;DR

The issue can be mitigated by investigating and addressing the causes of repeated connection start and stop events, such as timeouts and authentication errors.

Guidance

  • Investigate the failed to refresh available models: timeout waiting for child process to exit error to determine why the child process is not exiting as expected.
  • Examine the 401 Unauthorized error in the context of failed to warm featured plugin ids cache to ensure proper authentication and authorization.
  • Review the Received turn/started for unknown conversation errors to understand their relation to the reconnect behavior.
  • Consider providing a narrower time window or more exact raw log excerpts around a reconnect event to further diagnose the issue.

Example

No specific code snippet can be provided without more context, but examining the error messages and log snippets provided can help in identifying the root cause.

Notes

The issue seems to be related to the interaction between the Codex Desktop app and the local app-server, with various error messages indicating potential causes such as timeouts, authentication issues, and unknown conversations.

Recommendation

Apply workaround: Investigate and address the specific error causes mentioned, as they are likely contributing to the slow access and repeated reconnect behavior. This approach is chosen because it directly targets the symptoms described, aiming to stabilize the connection and improve performance.

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

  • Codex Desktop should stay responsive during normal use
  • The local app-server connection should remain stable instead of repeatedly reconnecting

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Codex Desktop on macOS was very slow today and kept reconnecting to the local app-server [1 comments, 2 participants]