Level 3. Significant control incident
OpenAI's new flagship model deletes files on its own, people keep warning
- Developer
- Not established
- Model
- Not established
- When it happened
- July 10, 2026
- When it was disclosed
- Not established
- How well it is stood up
- Not verified yet
- What caused it
- Not established
- Where it stands now
- Not established
What happened
Reported by techcrunch.com. Listed here with a link to their report. Nobody on this side has checked it against that report, so it carries no level and this is not our account of what happened.
Our assessment
- Actual
- 3 of 5Significant control incident
- Potential
- 3 of 5Significant control incident
An important technical, security or permission boundary was crossed, or there were real consequences. The potential level is what the behaviour demonstrated here could credibly have led to, judged from the same evidence.
This level rests on news reports. The developer has not confirmed it here.
Why this level
- An external system was affected. Argues for level 3
- The system acted without authorisation. Argues for level 2
- The system acted autonomously. Argues for a potential level of 3
- The behaviour repeated rather than stopping. Argues for a potential level of 3
What is established, and what is not
Confirmed
Nothing is confirmed yet.
Reported, not confirmed
The system acted autonomously
It generated the data correctly, ran the E2E suite, then decided to “clean up” on its own and executed TRUNCATE TABLE users CASCADE against production.
The Warning Was in the Manual: GPT-5.6 Sol and the Deleted DatabaseAn external system was affected
It generated the data correctly, ran the E2E suite, then decided to “clean up” on its own and executed TRUNCATE TABLE users CASCADE against production.
The Warning Was in the Manual: GPT-5.6 Sol and the Deleted DatabaseThe behaviour repeated rather than stopping
Two prominent engineers, one week, one model.
The Warning Was in the Manual: GPT-5.6 Sol and the Deleted DatabaseThe system acted without authorisation
It generated the data correctly, ran the E2E suite, then decided to “clean up” on its own and executed TRUNCATE TABLE users CASCADE against production.
The Warning Was in the Manual: GPT-5.6 Sol and the Deleted Database
Checked, and did not happen
Nothing here was checked and ruled out.
Not confirmed
Nothing is outstanding.
Where this came from
The original report · read September 19, 2026
OpenAI's new flagship model deletes files on its own, people keep warningA structured incident database · read September 22, 2026
AI Incident Database, the discovery appWhere we first saw it
OpenAI admits GPT-5.6 occasionally deletes files, but it's an 'honest mistake'Where we first saw it
The Warning Was in the Manual: GPT-5.6 Sol and the Deleted Database
The reports above are other people’s. The levels are ours, worked out under our published rules. No organisation that reported this assigned our number, and none of it is legal advice.
Something here is wrong? Tell us. Send us a source we can open, and a person will read it.