Bug Report — Codex runtime bundle not provisioned (bundleVersion=null)
Open 💬 2 comments Opened May 5, 2026 by Recred-lab
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
Description
When attempting to install or reinstall Codex workspace dependencies in the Codex Desktop App, the process fails and the diagnostic output shows:
bundleVersion = null
installed = false
problemCount = 1
The runtime bundle is not provisioned, preventing bundled workspace tools/dependencies from becoming available.
Steps to reproduce
- Open Codex Desktop App.
- Go to Settings -> Configuration -> Workspace Dependencies.
- Click "Diagnose" or "Reinstall".
- Observe that reinstall fails and the runtime bundle is not loaded.
Expected behavior
- Runtime bundle should be downloaded/provisioned.
- A valid bundle version should be registered, e.g.
bundleVersion=0.x.x. - Workspace dependencies should become installed/operational.
Actual behavior
- Runtime is not downloaded or not recognized.
bundleVersionremainsnull.- Workspace dependencies remain unavailable.
Technical notes
This appears to be a runtime bundle provisioning failure. It does not look like a local Node/Python execution issue.
Observed locally:
- Codex feature flag
workspace_dependenciesis enabled. - Bundled local Node runs successfully:
v24.14.0. - Bundled local Codex CLI runs successfully.
- Network from bundled Node reaches OpenAI/GitHub endpoints.
- Temporarily relaxing Windows Defender exclusions and the Codex sandbox firewall block did not change the result.
- Logs continue to show
bundleVersion=null installed=false problemCount=1.
Possible causes:
- backend/API not returning the runtime bundle config
- broken client release/runtime provisioning path
- workspace bootstrap failure before install starts
Troubleshooting performed
- Reinstalled/repaired Codex Desktop App through Microsoft Store/winget.
- Verified local bundled binaries exist under
%LOCALAPPDATA%\OpenAI\Codex\bin. - Verified bundled Node executes successfully.
- Verified Git is installed and available.
- Tried running/reinstalling as administrator.
- Temporarily disabled Codex sandbox outbound firewall block and added temporary Defender exclusions for Codex/Node, then restored original security settings.
- Tested in the configured workspace after reinstall/repair.
Issue persists.
Environment
- OS: Windows 10.0.19045 x64
- Codex Desktop App release:
codex@26.429.30905 - Microsoft Store package:
OpenAI.Codex_26.429.3425.0_x64__2p2nqsd0c76g0 - Installation: Microsoft Store / Desktop App
- Auth method: ChatGPT
- Network: no VPN/proxy configured
Impact
Blocks Codex workspace dependency usage entirely because the runtime bundle is unavailable.
Suspected root cause
Runtime bundle provisioning failure, likely backend/API config or client release issue rather than a local environment problem.
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I am seeing the same workspace dependency/runtime issue on Windows.
Feedback correlation ID:
2c90759b-79ad-4352-b0bf-47ea7a373e9aCodex Desktop package:
OpenAI.Codex_26.506.3741.0_x64__2p2nqsd0c76g0Symptoms:
primary_runtime_dependencies_diagnose_finished bundleVersion=null installed=false problemCount=1unsupported feature enablement 'workspace_dependencies'Failed to list primary runtime archiveRelated issue: #19770, because the local logs also show the app trying to enable
workspace_dependencieseven though the app-server reports it as unsupported.Additional local validation:
26.506.11943downloads successfully.ae40ccd28f101c148e245c56a34c99e3a04b92aaf0711410492fd6a44e19725cThis still leaves Codex Desktop reporting dependencies as not installed, which points to the Desktop/runtime provisioning path or feature-flag/app-server mismatch rather than a basic local dependency failure.