codex - 💡(How to fix) Fix Bug Report — Codex runtime bundle not provisioned (bundleVersion=null) [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#21116Fetched 2026-05-05 05:53:25
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1

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.

Root Cause

Blocks Codex workspace dependency usage entirely because the runtime bundle is unavailable.

Code Example

bundleVersion = null
installed = false
problemCount = 1
RAW_BUFFERClick to expand / collapse

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

  1. Open Codex Desktop App.
  2. Go to Settings -> Configuration -> Workspace Dependencies.
  3. Click "Diagnose" or "Reinstall".
  4. 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.
  • bundleVersion remains null.
  • 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_dependencies is 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: [email protected]
  • 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.

extent analysis

TL;DR

The most likely fix involves investigating and resolving the runtime bundle provisioning failure, potentially related to backend/API configuration or client release issues.

Guidance

  • Verify the Codex Desktop App's backend/API configuration to ensure it returns the correct runtime bundle config.
  • Check the client release/runtime provisioning path for any breaks or issues that might prevent the runtime bundle from being downloaded or recognized.
  • Investigate the workspace bootstrap process to determine if it fails before the install process starts, causing the bundleVersion to remain null.
  • Consider testing the Codex Desktop App on a different environment or network to isolate if the issue is specific to the current setup.

Example

No specific code snippet can be provided without further information on the Codex Desktop App's internal workings. However, checking the app's configuration files or logs for any errors related to runtime bundle provisioning might yield useful insights.

Notes

The issue seems to be related to the Codex Desktop App's ability to provision the runtime bundle, which is crucial for workspace dependencies. Given the troubleshooting steps already taken, the next steps should focus on the app's interaction with its backend/API and the client release/runtime provisioning path.

Recommendation

Apply workaround: Given the suspected root cause is related to runtime bundle provisioning failure, likely due to backend/API config or client release issues, attempting to manually provision the runtime bundle or checking for updates to the Codex Desktop App might provide a temporary workaround until a permanent fix is available.

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

  • 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.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING