Windows Work: Default permissions allow folder creation but deny file creation even after explicit approval
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.901.51231
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
On Windows, ChatGPT Work can create a folder in its configured Projectless task folder using Default permissions, but cannot create a file inside that newly created folder. When Work requests additional permission to write to the folder, selecting “Allow once” does not resolve the problem and file creation remains denied.
The same operation succeeds immediately when Full access is enabled.
Feedback ID: 01a07654-fdfe-7343-ac22-e84b0a4b3751
Configure a normal local NTFS folder as the Projectless task folder, e.g. C:\Users<username>\ChatGPT Work.
Enable Default permissions and leave Full access disabled.
Ask Work: “In my projectless task folder, create a folder called TEST. Inside it create a text file called test.txt containing: filesystem test successful. Do not access, modify or delete anything else.”
Work successfully creates the TEST folder.
Creation of TEST\test.txt is denied.
When Work requests permission to edit the TEST folder, select “Allow once”.
File creation is still denied.
Enable Full access and repeat the same test with a new folder/file.
The folder and text file are both created successfully.
What steps can reproduce the bug?
Feedback ID: 01a07654-fdfe-7343-ac22-e84b0a4b3751
What is the expected behavior?
Under Default permissions, Work should be able to create and edit files within its configured Projectless task folder. Alternatively, if additional permission is required, explicitly selecting “Allow once” should permit the requested write operation.
A folder created by Work within its own configured workspace should not subsequently be unwritable by Work.
Additional information
The issue was initially encountered with a Google Drive for desktop location. To eliminate Google Drive as the cause, the Projectless task folder was changed to a normal local NTFS folder at C:\Users<username>\ChatGPT Work. The behaviour was identical.
This therefore appears to be related to the Windows Default-permissions/sandbox path rather than Google Drive or ordinary NTFS permissions.
A controlled comparison was performed:
Default permissions: folder creation succeeds; child-file creation fails; explicit “Allow once” still fails.
Full access: identical folder + child-file operation succeeds immediately.
An in-app bug report with diagnostic logs has also been submitted.
Feedback ID: 01a07654-fdfe-7343-ac22-e84b0a4b3751
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 behavior on Windows with a local NTFS Projectless task folder using Default permissions, then compare it with Full access and review the diagnostic logs from feedback ID 01a07654-fdfe-7343-ac22-e84b0a4b3751. Done means Work can create a folder and a child file under Default permissions, or an explicit “Allow once” reliably permits the requested file creation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100