codex - 💡(How to fix) Fix Codex Desktop: resume conversation and model settings fail when cloud config bundle times out

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…

Codex Desktop repeatedly fails to resume remote conversations and sometimes fails when updating model/reasoning settings.

The error is:

failed to load configuration: timed out waiting for cloud config bundle after 15s

This looks like a Desktop-side config sync/load problem. CLI switching works, but the Desktop path fails.

Error Message

The error is:

Root Cause

Codex Desktop repeatedly fails to resume remote conversations and sometimes fails when updating model/reasoning settings.

The error is:

failed to load configuration: timed out waiting for cloud config bundle after 15s

This looks like a Desktop-side config sync/load problem. CLI switching works, but the Desktop path fails.

Code Example

failed to load configuration: timed out waiting for cloud config bundle after 15s

---

method=thread/resume
method=config/batchWrite
Failed to update model and reasoning effort
failed to load configuration: timed out waiting for cloud config bundle after 15s
RAW_BUFFERClick to expand / collapse

Summary

Codex Desktop repeatedly fails to resume remote conversations and sometimes fails when updating model/reasoning settings.

The error is:

failed to load configuration: timed out waiting for cloud config bundle after 15s

This looks like a Desktop-side config sync/load problem. CLI switching works, but the Desktop path fails.

Environment

  • Codex Desktop on macOS
  • Remote conversation resume in Desktop
  • Model/reasoning setting updates in Desktop settings
  • CLI path appears unaffected

Steps to reproduce

  1. Open Codex Desktop.
  2. Try to resume a remote conversation.
  3. Or open model settings and change default model / reasoning effort.
  4. Observe repeated failure.

Actual result

The app logs repeated failures such as:

method=thread/resume
method=config/batchWrite
Failed to update model and reasoning effort
failed to load configuration: timed out waiting for cloud config bundle after 15s

Expected result

Desktop should load the cloud config bundle, resume the conversation, and persist model/reasoning settings successfully.

Notes

  • The issue is reproducible across multiple attempts in the same session.
  • This looks different from a model/provider failure; the failure happens before the conversation resumes or settings persist.
  • CLI can still switch models successfully, which suggests the bug is specific to the Desktop config/resume path.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING