Codex macOS startup failure: unsupported feature enablement `workspace_dependencies`

[SnowfallHD]

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

26.422.20832

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.4.0 arm64 arm

What issue are you seeing?

Codex macOS app fails to start after update. Logs repeatedly show:

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

account/read succeeds, but startup fails immediately after trying to enable workspace_dependencies.

Versions:

• Codex app (About): 26.422.20832
• Codex bundled CLI: codex-cli 0.124.0-alpha.2
• Runtime selected in logs: codex-primary-runtime 26.423.10653

Notes:

• ChatGPT macOS app works
• ChatGPT web works
• Killing processes and resetting app cache/state did not resolve

What steps can reproduce the bug?

1. Update Codex via in-app updater.
2. Quit Codex.
3. Launch Codex.

Actual result: Codex fails during startup and logs unsupported feature enablement workspace_dependencies repeatedly. ChatGPT macOS app opens normally.

Minimal repro: just launch Codex.

I cannot provide session id/context window usage because the app never loads a workspace or starts a session. Logs are available under ~/Library/Logs/com.openai.codex/YYYY/MM/DD (redacted).

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

What is the expected behavior?

Codex should launch successfully on macOS, connect to the local host/runtime without errors, and load the workspace selection UI/dashboard.

It should not try to enable unsupported features (workspace_dependencies) unless the runtime supports them.

Additional information

What I already tried:

• kill Codex/ChatGPT processes
• cleared caches and app state
• tried reopening

Codex still fails at startup with the same log message above. ChatGPT app and web continue to work.

(Logs taken from ~/Library/Logs/com.openai.codex/YYYY/MM/DD; redacted local usernames.)

[github-actions]

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

• Codex VS Code extension fails to enable realtime_conversation; new chats cannot switch model and Output is flooded with worker warnings #18842
• [Bug] reqwest HTTP clients missing User-Agent override → Cloudflare 403 from HKG edge on Codex Desktop 26.422.x #18456

Powered by Codex Action

[SnowfallHD]

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

• Codex VS Code extension fails to enable realtime_conversation; new chats cannot switch model and Output is flooded with worker warnings #18842
• Windows desktop app regression after in-app upgrade: settings/language break, slash commands stop working, Fast Mode missing #18456

Powered by Codex Action

Not a duplicate of the suggested issues.

#18842 is related to the VS Code extension on Windows (realtime_conversation + worker warnings), and #18456 is a Windows desktop app regression after upgrade (settings/slash commands/Fast Mode).

This issue is specific to the macOS Codex desktop app failing at startup with:

unsupported feature enablement workspace_dependencies

The failure occurs before any workspace/session loads, and account/read succeeds, indicating a runtime/feature mismatch rather than a UI or extension issue.

Happy to provide additional logs or test fixes if needed.

[etraut-openai]

It sounds like you have an invalid feature flag entry in your config file. Open ~/.codex/config.toml and search for "workspace_dependencies".

[HRussellZFAC023]

It's bricked for me too, deleting the config file did not help. Bricked in codex app also in vs code and also antigravity. It's only a problem since updating

[HRussellZFAC023]

Also I noticed it's eating lots of ram

[entif-ai]

Same here. No reference to "workspace_dependencies" in the config.toml; just totally bricked as of today.

Hate to be "that guy", but... maybe Codex's coders ought to do less vibe coding and more hands-on testing.

EDIT: I updated the CLI (had to rm the Brew cask manually), logged out and then back in. I'm all good now.