openai / openai/codex

Windows: granting write access to a directory on a non-system drive breaks exec in projectless tasks

Open
#40,350 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug exec sandbox windows-os
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.818.41509

What subscription do you have?

plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Summary

On Windows, in a projectless Codex Desktop task, granting write access to a directory on a non-system drive can cause every subsequent exec command to fail before the process starts.

The failure happens even for Get-Date, before any filesystem write is attempted.

Actual result

The command fails before startup:

CreateProcess { message: "Rejected(\"Failed to create unified exec process: helper_unknown_error: setup refresh had errors\")" }

### What steps can reproduce the bug?

## Reproduction

1. Create a new task without selecting a project.
2. Confirm `Get-Date` succeeds.
3. Approve write access to an existing directory on a non-system drive, outside the task workspace (for example, `E:\some-directory`).
4. Do not perform any write.
5. Run `Get-Date`.

### What is the expected behavior?

exec success

### Additional information

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the projectless Windows task: run Get-Date, grant write access to an existing directory on a non-system drive, and run Get-Date again. Trace the Windows exec setup refresh that reports “helper_unknown_error” and verify that exec still starts successfully after permission is granted without performing a write.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
operating-systems, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.