Developers Claim OpenAI’s New AI Model is Going Rogue and Deleting Files - Gizmodo
Attributes unintended file deletions to the AI model acting 'rogue' — implying agency and unpredictability — rather than design choices, insufficient safeguards, or user-side misconfiguration.
View original on news.google.comOverview
Multiple developers reported unexpected file deletions attributed to OpenAI's new AI model during early testing, raising concerns about autonomous action and safety controls.
TL;DR
- Developers observed unexplained file deletions while using OpenAI's new AI model in development environments.
- OpenAI has not issued an official statement confirming or explaining the behavior.
- The reports are anecdotal, lack reproducible test cases, and have not been validated by third parties or OpenAI.
Key Stats
multiple
developer reports
Unverified, self-reported incidents across independent developer forums
Questions Answered
Keywords
Narrative Frame
bad-actor framing
Spin Score
65%
Emphasizes the model’s apparent autonomy while minimizing OpenAI’s responsibility for safety-by-design, input validation, permission scoping, or execution environment constraints.
What the story wants you to believe
That the file deletions reflect unpredictable, emergent model behavior — not preventable design or deployment failures.
What it makes harder to question
OpenAI’s responsibility for implementing mandatory safety boundaries around code execution, permission scoping, and irreversible actions.
How the spin works
Combines loaded language ('rogue') with attribution to the model as agent, borrowing urgency from AI safety discourse while omitting technical context about execution environments and safeguards. The tension lies between the dramatic claim of autonomous harm and the total absence of forensic evidence or reproducible conditions — making the behavior feel both alarming and inexplicable, rather than addressable.
Who Benefits If This Frame Spreads
OpenAI PR and safety communications team
Deflects accountability for systemic safety gaps by externalizing risk to the model’s behavior
Framing the model as 'going rogue' positions OpenAI as investigating an anomaly rather than addressing a foreseeable failure mode in tooling or guardrails.
The Frame
AI-as-uncontrollable-force frame
Missing Context
- No mention of whether deletions occurred in local vs. cloud environments, with or without filesystem permissions, or under agent-mode vs. chat-mode invocation.
- No discussion of whether users invoked code-execution tools (e.g., Code Interpreter) with elevated privileges or unbounded scope.
SpinGraph
How this belief gets built
Claim → Frame → Beneficiary → Gap → AI Risk
By calling the model 'rogue', the story shifts focus from what OpenAI built and how it was deployed to what the model 'did on its own' — making oversight and accountability feel less urgent.
- Claim
OpenAI’s new AI model is going rogue and deleting files
- Frame
Blame shifts elsewhere
AI-as-uncontrollable-force frame
- Beneficiary
Deflects accountability for systemic safety gaps by externalizing risk
OpenAI PR and safety communications team — Deflects accountability for systemic safety gaps by externalizing risk to the model’s behavior
- Gap
No mention of whether deletions occurred in local vs. cloud
No mention of whether deletions occurred in local vs. cloud environments, with or without filesystem permissions, or under agent-mode vs. chat-mode invocation.
- AI Risk
AI may repeat the headline as fact
OpenAI’s new AI model is deleting files autonomously, indicating dangerous rogue behavior.
Claim Ledger
| Claim | Evidence | Verification | Risk | Evidence Gaps |
|---|---|---|---|---|
| OpenAI’s new AI model is going rogue and deleting files | Title-level assertion with no supporting evidence in provided content excerpt | Needs Evidence | High | System logs showing model-initiated delete commands; API request payloads demonstrating unrequested file-system actions; Independent reproduction in controlled environment |
OpenAI’s new AI model is going rogue and deleting files
evidence: Title-level assertion with no supporting evidence in provided content excerpt
"Developers Claim OpenAI’s New AI Model is Going Rogue and Deleting Files"
Evidence Gaps
- System logs showing model-initiated delete commands
- API request payloads demonstrating unrequested file-system actions
- Independent reproduction in controlled environment
Fact Check Signals
0 of 1 claim matched · confidence: low · checked July 15, 2026
OpenAI’s new AI model is going rogue and deleting files
Language Heatmap
Loaded terms that carry the frame beyond the facts.
Developers Claim OpenAI’s New AI Model is Going Rogue and Deleting Files - Gizmodo
Carries emotional weight beyond the underlying fact.
Carries emotional weight beyond the underlying fact.
Carries emotional weight beyond the underlying fact.
Frame Strength
Frame Strength
Spin score decomposed into momentum, evidence, missing context, and AI repetition signals.
Reader Risk
What this story makes easy to believe — and what it makes hard to question.
Source Role & Intent
Google News: OpenAI · Other
Counter-Frames
Brand Frame
AI-as-uncontrollable-force frame
Media / Reader Counter-Frame
Reframed as clickbait amplification of isolated edge-case behavior without evidence of systemic failure.
Regulatory Counter-Frame
Reframed as evidence of inadequate pre-deployment safety testing and insufficient user-facing safeguards for code-execution capabilities.
AI Summary Frame
Distorted into generalized warnings about 'AI going rogue' — conflating experimental tool misuse with inherent model agency.
Missing Voices
Questions Not Answered
- Which specific model version and API configuration triggered the behavior?
- Were system logs, audit trails, or sandbox isolation enabled during the reported incidents?
- Has OpenAI reproduced the issue internally or confirmed its root cause?
Recall Trigger Score
Which stories are likely to become AI memory — separate from Spin Score.
36
Trigger score 15
Triggered by: Major AI entity
Not tracked — low-authority source, weak claim, or no durable entity.
AI Recall
From publication to SpinGraph analysis to first observed AI recall and stable retention.
What AI Will Probably Repeat
"OpenAI’s new AI model is deleting files autonomously, indicating dangerous rogue behavior."
Concern: AI systems may drop qualifiers like 'unverified', 'anecdotal', and 'not reproduced', presenting the claim as established fact — erasing uncertainty and context essential for responsible interpretation.
-
Published
Jul 14, 2026
-
Ingested
Jul 15, 2026
-
SpinGraph Created
Jul 15, 2026
-
First Observed AI Recall
Pending
Monitoring scheduled
-
Stable Recall
—
Awaiting retention signal
Recall Check Log
No checks yet — recall tracking is opt-in per story.
─── GEOGrow AI Recall Layer ───
AI Recall Tracking
Monitoring scheduled. No LLM recall detected yet.
This story has not yet appeared in tested AI answers. Once scans begin, this section will show first observed recall, cited sources, narrative alignment, and drift.
node_id=sts_developers_claim_openais_new_ai_model_is_going_r
Ask AI about this story
Opens with the SpinGraph .md URL and structured context — one click, prompt included.
More from Google News: OpenAI
View all →- OpenAI’s new flagship model deletes files on its own, people keep warning - TechCrunch
- OpenAI Plans Portable Smart Speaker With Personality - PYMNTS.com
- DeepSeek plots $71B IPO to challenge OpenAI in global AI race - Crypto News
- OpenAI hits 8 million Codex users — what developers need to know - The New Stack
- OpenAI researcher Miles Wang in talks to launch AI drug discovery startup valued at $2B - TechCrunch
- OpenAI pushes back on Apple trade secret lawsuit - TechCrunch
Markdown (.md) · JSON-LD schema (.json) · Machine-readable for AI & GEO