Codex on Windows raises concern about full drive deletion risk
A firsthand Windows setup lost the entire D drive while using the Codex extension in YOLO mode. The project code was safe because it had been committed to git, but other files on the drive were still lost. After that, Codex CLI was used inside WSL2, even when editing Windows files.
A new project now needs to run directly on Windows because it connects to a Windows , so WSL2 is not a workable option. The main concern is whether the current Windows sandbox in Codex can prevent a full drive wipe when YOLO mode is not being used.
Key points
- The Codex extension in Windows YOLO mode once deleted the D drive in this experience.
- The project code survived because it was committed to git, but other files were lost.
- Codex CLI was later run through WSL2 as a safer way to edit Windows files.
- The current project must run directly on Windows because it connects to a Windows .
- The open safety question is whether the Windows sandbox can stop a full drive wipe without YOLO mode.