›_ Codex Issues
Codex Issues / #30999

Windows Codex App Workspace runtime stuck as “Not installed” although Node runtime exists and Full access/network are available

Open 💬 3 comments Opened Jul 3, 2026 by a60153lin-cpu
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

目前版本：未安裝

What subscription do you have?

Plus

What platform is your computer?

Windows

What issue are you seeing?

Workspace runtime after reinstall still shows as not installed. Local cua_node runtime and manifest exist under C:\Users\zz118\AppData\Local\OpenAI\Codex\runtimes, but Codex workspace dependency query returns No bundled workspace runtime dependencies are configured yet. Global state remains stuck at electron:onboarding-primary-runtime-install-requested=true and electron:onboarding-primary-runtime-install-ready=false. Full access is enabled, network-disabled env var is empty, and plugin sync lock is not present.

What steps can reproduce the bug?

  1. Configure Codex with CODEX_HOME=D:\AI_Apen\Codex_HQ\.codex and CODEX_SQLITE_HOME=D:\AI_Apen\Codex_HQ\.codex_sqlite.
  2. Open Codex App and trigger Workspace runtime reinstall.
  3. Observe that Node runtime files are created under C:\Users\zz118\AppData\Local\OpenAI\Codex\runtimes\cua_node\1b23c930bdf84ed6.
  4. Query workspace dependencies from Codex.
  5. Observe that dependency query still reports no bundled workspace runtime dependencies configured.
  6. Check .codex-global-state.json; runtime install remains requested=true and ready=false.
  7. Workspace UI still shows current version as not installed.

What is the expected behavior?

After Workspace runtime reinstall completes and runtime files exist, Codex should register bundled workspace runtime dependencies, update global state to ready, and show the installed Workspace runtime version in the UI.

Additional information

codex_workspace_runtime_bug_report_260703.md

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 1 month ago

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

  • #30711
  • #30280

Powered by Codex Action

edwardchin811227 · 1 month ago

I can reproduce the same failure on another Windows installation.

Environment

  • Codex Desktop runtime reports version 26.707.31428
  • Windows (using a mapped NAS workspace: Y:\3E 客人资料\AC03)
  • Local py.exe is available, but that does not satisfy the managed workspace-runtime requirement.

Actual result
Calling the workspace dependency loader returns exactly:

No bundled workspace runtime dependencies are configured yet.

I fully quit and restarted Codex Desktop, then repeated the check in a new task. The result is unchanged.

Expected result
Codex Desktop should install/register its bundled workspace runtime (including the managed Python path) or expose an actionable Diagnose/Reinstall workflow and a specific error. Skills that require the managed runtime cannot run while the loader returns this state.

feng33d · 1 month ago

I can reproduce this on the current Windows desktop package, and it also blocks the built-in custom pet workflow.

Environment

  • Codex desktop package: OpenAI.Codex_26.707.9981.0_x64
  • Codex command runner: 0.144.2
  • Windows desktop app
  • Flow: Settings > Pets > Create your own pet

Reproduction

  1. Open Settings > Pets.
  2. Choose Create your own pet.
  3. Let the app install/load hatch-pet and open the generated pet task.
  4. Ask the task to create a custom v2 pet.
  5. The required workspace-runtime preflight calls load_workspace_dependencies.

Actual result

The tool returns:

No bundled workspace runtime dependencies are configured yet.

The hatch-pet workflow requires the bundled Python/Pillow runtime and explicitly cannot fall back to system Python. As a result, generation, validation, packaging, and installation never begin, and the local pets directory remains empty.

This reproduced in two freshly created pet tasks. Restarting the app, running the Windows package repair path, and checking Microsoft Store for updates did not change the result; no newer app version was offered.

Expected result

The Create your own pet flow should automatically provision/register the bundled workspace dependencies, or show an actionable in-app recovery/setup step, so the generated task can complete the v2 pet workflow.

No user images or private filesystem paths are included in this report.