[Critical Data Loss] Unsafe recursive deletion caused permanent loss of project source code

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

Powered by Codex & OWL 版本 26.901.51231 发布于 2026年9月6日

What subscription do you have?

Plus

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

Codex executed an unsafe recursive Windows deletion command and deleted source files from multiple projects on my J: drive.

This caused actual data loss, including uncommitted local changes. The deletion exceeded the intended .fast-ide-runtime cleanup scope and affected multiple unrelated project directories.

The source code could not be successfully recovered. This resulted in permanent data loss, not merely temporary file deletion.

What steps can reproduce the bug?

Feedback ID: 01a07f6b-a5da-7200-a16e-2acd63974190

What is the expected behavior?

Codex should restrict the operation to the explicitly resolved target directories.

Before executing a recursive deletion, Codex should:

• Resolve and display every target path.
• Block targets outside the requested root directory.
• Require explicit confirmation for recursive deletion.
• Refuse to delete project source directories or unrelated projects.

Additional information

This is a critical data-loss incident, not a normal build or configuration issue.

TestDisk did not successfully recover the affected projects. Although a disk image was created and a large number of files were extracted, the recovered data was incomplete and unusable for restoring the original projects. Important source files, project structures, and uncommitted local changes remain missing.

The lost data included important uncommitted development work. There was no usable backup and IntelliJ Local History could not restore the missing source code. As a result, this incident caused permanent loss of project data and significant recovery and development costs.

I request:

1. Immediate escalation to OpenAI engineering, safety, and support teams.
2. Preservation and review of all relevant Codex tool-execution and audit logs.
3. A formal explanation of why the destructive command was generated and executed without strict path-scope validation or confirmation.
4. Assistance with professional data-recovery costs.
5. A formal review of compensation for the lost work, recovery expenses, and resulting business impact.

Please treat this as a severe Codex safety incident involving destructive file-system access and unrecovered source-code loss.

Start with Feedback ID 01a07f6b-a5da-7200-a16e-2acd63974190 and the relevant tool-execution or audit logs to identify the deletion command and resolved targets. Review the Windows recursive-deletion path and its scope checks, then add regression coverage showing that targets outside the requested root and project source directories are blocked.