Critical Data Loss Issue in Codex App for Windows – Agent Executed File Deletion Outside Project Directory

I came here after Codex wiped ~240GB of data from my D:\Downloads folder (after having mapped C:\Users\myuser\Downloads , Documents , Videos , etc. to D:\ as I had more space there), other folders that were important to me, and other useful data such as textures, game files, source code files (python, C++).

It all begun when I started using the Codex app today and tried to make a simple powershell clone with a CTRL+K functionality, similar to Cursor. Codex (GPT 5.4 XHigh Fast) begun downloading the powershell source code to start inspecting it and see what we can do. I asked it to move it out of C:\ to D:\ because that’s where I had more space. The codex agent listened and it tried doing so; running command after command. At first it was encountering some issues, and tried continuing. All of a sudden, I am met with a weird monologue from the agent: “The current shell session doesn’t have git on PATH, even though it was available earlier. I’m locating the Git executable explicitly and then cloning to D: with the full path.”

Git on PATH apparently did not exist anymore … the real nightmare was that it did not exist at all anymore . And the file wipe has already started. I had soon restarted my computer once I realized that accessing D:\Downloads was erroring out and my desktop had no icons anymore. I thought nothing to myself because Windows had display bugs like these and a restart would usually fix it. This is not the sweet rainbow world I was met with however.

Just 2 days ago when I checked, my D had ~180 GB remaining out of approx. 1 TB . After I restarted, I checked again and was met with a shocking 420 GB remaining. That’s 240 GB gone. Useful info … it was. No longer is.

As a matter of fact, I had Full Access turned on, because, in its sandboxed environment, it couldn’t create any files without running python scripts, so I just thought I’d let it more priviliged. It was fine initially; a day later (which is today morning), disaster struck.

The worst thing is that this can happen to you too; which is why I stopped using Codex (specifically the Microsoft Store Windows app). This has never happened with Cursor, Windsurf, CC, Warp, or anything you can imagine.

Not to mention that I have tried 4 different disk recovery tools and they have all failed, each telling me after copying the files back on my PC that the executables were corrupted, and not only them, but every single file that was not a .json or .txt file.

F* you Codex