Windows ARM64: Workspace Dependencies remain "Not installed", preventing custom pet creation and import
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.715.10079.0 (Microsoft Store)
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Windows 11 ARM64
What issue are you seeing?
Workspace Dependencies always remains "Not installed", even after a complete clean reinstall of the application.
This prevents local pet workflows that require the bundled Workspace runtime.
The issue is not limited to the hatch-pet skill.
It also affects:
- creating new custom pets;
- importing pets previously created in the web version;
- continuing existing pet projects locally;
- validating pet assets.
The application reports that the bundled workspace runtime is unavailable.
Example:
The bundled workspace Python/Pillow runtime is unavailable.
The workflow requires the bundled Python/Pillow runtime
and does not allow system Python as a substitute.
Another symptom is that only the cua_node runtime is installed, while the primary workspace runtime is never provisioned.
Workspace Dependencies always returns to:
Not installed
What steps can reproduce the bug?
Feedback ID: no-active-thread-01a01576-5270-7832-bd18-a717a403b2a1
What is the expected behavior?
Workspace Dependencies should successfully install the bundled workspace runtime and display an installed runtime version.
After that, Codex should be able to:
- create custom pets;
- import pets created in the web version;
- continue existing pet projects;
- execute workflows that require the bundled workspace runtime.
Additional information
- Install Codex from the Microsoft Store on Windows 11 ARM64.
- Sign in.
- Open Settings → Configuration → Workspace Dependencies.
- Click Reinstall.
- Wait for the installation to finish.
- Workspace Dependencies immediately returns to "Not installed".
- Attempt to create a custom pet or import a pet created in the web version.
- The workflow stops because the bundled workspace runtime is unavailable.
I also tried:
- completely uninstalling Codex;
- deleting every OpenAI/Codex local folder;
- deleting
.codex; - deleting runtime caches;
- reinstalling from Microsoft Store;
- logging in again;
- installing WSL;
- rebooting;
- running Codex as Administrator.
The behavior never changes.
Device architecture is ARM64.
The application installs the Computer Use runtime (cua_node) successfully, but never provisions the bundled workspace runtime required by these workflows.
The problem persists after:
- clean uninstall;
- deleting all local OpenAI/Codex data;
- reinstalling from Microsoft Store;
- installing WSL;
- rebooting.
This appears to be a Workspace Dependencies provisioning issue rather than a problem with any individual pet skill.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Workspace Dependencies reinstall flow on Windows 11 ARM64 and inspect how the primary workspace runtime is provisioned compared with the installed cua_node runtime. Done means Reinstall leaves a workspace runtime installed and custom-pet creation, web-pet import, and existing local workflows no longer report the bundled Python/Pillow runtime as unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100