Remove-Item fails with Full access while .NET deletion succeeds

Reproduce this on Windows 11 in the Codex desktop app with Full access and no selected workspace, comparing PowerShell Remove-Item with the .NET Directory API for the same empty folder. Trace the normal deletion workflow and its workspace-permission decision; done means a narrowly scoped deletion uses the standard method safely without incorrectly reporting that it is blocked.

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

26.721.41059

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows 11 x64 — Microsoft Windows NT 10.0.26200.0

What issue are you seeing?

With "Full access" enabled, Codex failed to delete an empty folder using PowerShell Remove-Item and reported that delete commands outside the active workspace were blocked, even though no project or workspace was selected.

I started a new chat without selecting a project or workspace and asked Codex to delete this empty folder:

C:\Users\AMD4x\Desktop\New folder

The initial deletion attempt using Remove-Item failed, and Codex responded:

"I couldn’t remove the folder because this environment blocks delete commands outside the active workspace."

In the same chat, I then asked Codex to delete the same folder using the .NET Directory API. The deletion succeeded.

This suggests inconsistent command handling with Full access enabled: the PowerShell Remove-Item attempt failed, while System.IO.Directory.Delete successfully deleted the same folder in the same session.

What steps can reproduce the bug?

1. Open the Codex desktop app on Windows.
2. Start a new chat without selecting a project or workspace.
3. Select "Full access" from the permissions control.
4. Create an empty folder outside any selected workspace, for example:

C:\Users<username>\Desktop\CodexTestFolder

5. Ask Codex to delete the folder without specifying a deletion method.
6. Codex attempts the deletion using PowerShell Remove-Item, but the operation fails. It then reports that delete commands outside the active workspace are blocked, even though no workspace is selected.
7. In the same chat, ask Codex to delete the same folder using the .NET Directory API.
8. The .NET deletion succeeds.
9. Confirm that "Full access" remains enabled throughout the test.

What is the expected behavior?

With "Full access" enabled and a clear, narrowly scoped deletion request, Codex should complete the operation through its normal deletion workflow without requiring the user to specify an alternative API.

If Remove-Item was restricted because the model previously performed overly broad or unsafe deletions, the preferred solution is to improve the model's deletion judgment and safeguards—such as validating the exact target, limiting the deletion scope, avoiding broad recursive patterns, and requesting confirmation when appropriate—then restore reliable use of the standard deletion method.

The successful .NET deletion demonstrates that the requested operation was permitted and technically possible. It should not result in restricting the .NET API as well; instead, Codex's default deletion behavior should be made both safe and functional.

Additional information

No response