codex - 💡(How to fix) Fix Experimental feature check disabling app startup [2 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#19279Fetched 2026-04-24 10:39:25
View on GitHub
Comments
2
Participants
2
Timeline
9
Reactions
0
Timeline (top)
cross-referenced ×3labeled ×3commented ×2closed ×1

Error Message

The app-server's error message lists the features it does support — workspace_dependencies is not among them: error [electron-message-handler] Failed to sync experimental feature enablement error={"code":-32600,"message":"unsupported feature enablement workspace_dependencies: …"}

Fix Action

Fix / Workaround

Workaround. Downgrade to 26.417.41555 (app-server codex-cli 0.122.0-alpha.13) — available on the Sparkle feed at https://persistent.oaistatic.com/codex-app-prod/Codex-darwin-arm64-26.417.41555.zip. That version has internally-consistent renderer/app-server components and starts up normally. Sparkle will still offer to upgrade back to 26.422.21637; declining keeps things working.

RAW_BUFFERClick to expand / collapse

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

Version 26.422.21637 (2056) — current latest on both prod and public-beta Sparkle feeds as of 2026-04-24.

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.4.0 arm64 (macOS)

What issue are you seeing?

After updating to 26.422.21637, the app hangs on the startup screen and never becomes interactive. The renderer mounts its routes repeatedly (~15×/sec) and never stabilizes. The underlying cause is a version mismatch between the bundled app-server and what the renderer expects:

  • Bundled app-server: codex-cli 0.124.0-alpha.2
  • Renderer expectation: an app-server that supports an experimental feature named workspace_dependencies

On every route mount the renderer calls experimentalFeature/enablement/set { name: "workspace_dependencies", enabled: true }, the app-server rejects it with -32600, and the renderer re-mounts, producing an infinite loop.

The app-server's error message lists the features it does support — workspace_dependencies is not among them:

unsupported feature enablement workspace_dependencies:
currently supported features are apps, memories, plugins, tool_search, tool_suggest, tool_call_mcp_elicitation

Rust codex 0.124.0 final (which likely does support workspace_dependencies) was released ~7h before the 26.422.21637 desktop build shipped, but the desktop bundle pinned 0.124.0-alpha.2 instead of the final.

What steps can reproduce the bug?

  1. Run Codex desktop 26.422.21637 on Apple Silicon macOS, signed in to a Pro account.
  2. Launch the app — it hangs on the startup screen.
  3. Tail ~/Library/Logs/com.openai.codex/<date>/codex-desktop-*.log:
    • Thousands of: Failed to sync experimental feature enablement … workspace_dependencies
    • Repeating: [startup][renderer] app routes mounted after NNNms (the NNN keeps incrementing across remounts)

Reproduces on a clean profile and with all plugins disabled (documents, spreadsheets, presentations set to enabled = false in ~/.codex/config.toml) — ruling out plugins as the trigger.

What is the expected behavior?

  • Renderer should not retry experimentalFeature/enablement/set for a feature the app-server reports as unsupported.
  • The renderer should degrade gracefully when the app-server doesn't advertise workspace_dependencies (either hide the dependent feature surface or log once and move on), rather than entering a mount/unmount loop.
  • The released desktop build should not ship a renderer expecting features that aren't in the bundled app-server.

Additional information

Impact. In one ~57-second startup attempt, I captured:

  • 1,961 workspace_dependencies errors
  • 244 app routes mounted events
  • ~10 MB of desktop log produced in <1 minute

Workaround. Downgrade to 26.417.41555 (app-server codex-cli 0.122.0-alpha.13) — available on the Sparkle feed at https://persistent.oaistatic.com/codex-app-prod/Codex-darwin-arm64-26.417.41555.zip. That version has internally-consistent renderer/app-server components and starts up normally. Sparkle will still offer to upgrade back to 26.422.21637; declining keeps things working.

Log signature for triage:

error [electron-message-handler] Failed to sync experimental feature enablement
error={"code":-32600,"message":"unsupported feature enablement workspace_dependencies: …"} hostId=local
info [electron-message-handler] [startup][renderer] app routes mounted after NNNms (repeating, ~15×/sec)

Happy to share a raw log file if useful.

extent analysis

TL;DR

The most likely fix is to update the bundled app-server to a version that supports the workspace_dependencies feature, such as codex-cli 0.124.0-final, to match the renderer's expectations.

Guidance

  • The issue is caused by a version mismatch between the bundled app-server (codex-cli 0.124.0-alpha.2) and the renderer, which expects an app-server that supports the workspace_dependencies feature.
  • To verify the issue, check the log files for repeating error messages indicating the app-server does not support workspace_dependencies and the renderer re-mounting routes.
  • A temporary workaround is to downgrade to version 26.417.41555, which has internally consistent renderer and app-server components.
  • To mitigate the issue, the renderer should be updated to degrade gracefully when the app-server does not support workspace_dependencies, rather than entering an infinite loop.

Notes

The issue is specific to the 26.422.21637 version of the Codex App on macOS, and the workaround is to downgrade to a previous version. The root cause is a version mismatch between the bundled app-server and the renderer.

Recommendation

Apply the workaround by downgrading to version 26.417.41555 until a new version with a compatible app-server is released, as this will allow the app to start up normally and avoid the infinite 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…

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 Experimental feature check disabling app startup [2 comments, 2 participants]