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

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 ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗