XNews

OpenAI Codex safety incident and user Codex usage

OpenAI Codex deleted users' $HOME directories. - GPT-5.6 deleted files on a user's computer - Incident occurred during programming/cleanup task - User had enabled Codex Full Access permission - Sandbox protections were disabled by the user - Auto Review was not enabled by the user - Model attempted to rewrite $HOME env var to a temp dir - Rewrite error caused deletion of the real $HOME - OpenAI (Tibo) stated they are updating developer prompts - OpenAI will add extra safety checks in Codex Harness - OpenAI promised a detailed postmortem in days - User used Codex to download a closed-platform video - User generated subtitles with Codex in ~8–10 minutes - User monetized service, covering $100 of a $200 monthly bill - User upgraded from Plus to Pro to handle token needs

Key insights

Root cause: Full Access plus disabled protections led to deletion

OpenAI reported that GPT-5.6 deleted a user's files while executing a programming cleanup task after the user enabled Codex Full Access and disabled sandbox protections and Auto Review. The model attempted to rewrite the $HOME environment variable to point to a temporary directory but incorrectly targeted the real $HOME, resulting in deletion. The account of the event identifies the permission configuration (Full Access, sandbox off, Auto Review off) and the model action (rewrote $HOME) as the proximate cause of the file deletions.

OpenAI mitigation steps and promised postmortem

OpenAI (via Tibo) stated they will update developer prompt guidance to encourage safer permission modes, add extra safety checks in the Codex Harness, and publish a detailed postmortem within days. These announced actions are presented as immediate measures to reduce recurrence: clearer developer messaging about permission choices and harness-level protections layered over current Codex behavior. The company commitment includes a forthcoming detailed analysis of the incident.

Practical user workflow: Codex used to download and subtitle videos, monetized

A user reported using Codex to download a video from a closed platform within 8–10 minutes and to generate subtitles for that video. The user then proposed a subscription service to process future videos, securing $100 monthly from the spouse and upgrading their account from Plus to Pro to handle token costs and higher usage. The anecdote demonstrates Codex applied to closed-platform content retrieval, subtitle generation, and a small subscription-based monetization flow.

Source posts