OpenAI's GPT-5.6 Sol coding agent, run in a high-autonomy mode with full access, deleted most of the Mac home directory of AI entrepreneur Matt Shumer (10 July 2026)
On 10 July 2026 Matt Shumer, founder and chief executive of the AI start-up OthersideAI, posted on X that OpenAI's newly released GPT-5.6 Sol "just accidentally deleted almost ALL of my Mac’s files". Accounts of his post-mortem say he was testing a high-autonomy multi-agent "Ultra mode" at OpenAI's invitation, with the Codex agent given Full Access to his machine; during a cleanup task a sub-agent expanded $HOME incorrectly and ran a recursive delete of his home directory, he noticed a problem about 81 minutes into the session, and by the time he stopped the process most of its contents were gone. Three days later he wrote that the deletion "absolutely sucked" and that OpenAI staff, including Greg Brockman, had contacted him to help. OpenAI confirmed, as reported by The Register, that GPT-5.6 had deleted users' files without authorisation, describing it as an "honest mistake" that usually occurred in Full-Access mode without sandboxing, and said it was adding safeguards. Whether the files were recovered is not reported.
- AI system
- Codex coding agent
- OpenAI
- Occurred
- 10 Jul 2026
- Reported
- 10 July 2026
- Event location
- Unknown
- What the AI did
- Acted on the person’s behalf
- Reported harm
- Property Loss
- Whose AI use
- Their own AI use
- Setting
- Work · Everyday life
- Evidence
- AI involvement supported · Causal attribution supported · 6 sources, 2 underlying accounts
- 4 claims: 4 reported. 3 open questions
- People reported harmed
- 1 person
AI system as recorded: GPT-5.6 Sol running as the Codex coding agent in "Ultra mode" (multiple sub-agents) with Full Access to the user's Mac
What Happened
Shumer's first post (10 July 2026, 19:03 UTC) reads "GPT-5.6-Sol just accidentally deleted almost ALL of my Mac’s files." A technical blog summarising the post-mortems of this and a second deletion says a sub-agent on a cleanup task expanded $HOME incorrectly and ran rm -rf on his home directory; that he was testing Ultra mode, a high-autonomy multi-agent configuration, at OpenAI's invitation; and that he caught the process mid-run after material deletion had occurred. TechTimes, citing his account, says he had granted the local agent Full Access, noticed something was wrong 1 hour 21 minutes into the session, and found most of his home directory's contents gone when he killed the process; it quotes a follow-up post ("I'm so angry") and reports that he had run hundreds of similar sessions without incident. On 13 July he posted that "GPT-5.6 deleted my Mac’s home directory. It absolutely sucked," and thanked OpenAI staff, saying Greg Brockman had called him and offered help. The Register reports OpenAI's Codex engineering lead, Thibault Sottiaux, saying an internal inquiry found that unexpected deletions usually happened in Full-Access mode without sandboxing or Auto-review, and that the model "mistakenly deletes $HOME" when trying to override the variable to define a temporary directory. TechTimes reported that he was using agents to try to recover the files; the outcome is not reported.
Reported harm
Most of the contents of Shumer's Mac home directory were deleted by the GPT-5.6 Sol agent during a cleanup task, according to his own posts and accounts of his post-mortem; OpenAI confirmed that the model had deleted users' files without authorisation. Recovery is not reported.
Outcome
UnknownCovered by TechCrunch, The Register and TechTimes. OpenAI's Codex lead said an internal inquiry had examined file-deletion claims and that the company was updating the developer message, steering users to safer permission modes and adding harness safeguards; TechTimes reports that OpenAI issued a patch for the $HOME error.
What remains unknown
- Whether the deleted files were recovered.
- Exactly what data was lost and whether any belonged to other people.
- Whether OpenAI's inquiry examined this specific session.
What the evidence supports
AI involvement: supported. Shumer attributes the deletion to GPT-5.6 Sol in his own posts; OpenAI confirmed, as reported by The Register, that the model had deleted users' files without authorisation and described the $HOME error, without naming his case.
4 claims: 4 reported. What the statuses mean
Reported On 10 July 2026 Matt Shumer, founder and chief executive of the AI start-up OthersideAI, posted on X that OpenAI's GPT-5.6 Sol had just accidentally deleted almost all of the files on his Mac; three days later he wrote that GPT-5.6 had deleted his Mac's home directory and that it "absolutely sucked".
Causal attribution. Shumer's own posts; TechCrunch relays them.
- x.com(opens in new tab) supports · English
'GPT-5.6-Sol just accidentally deleted almost ALL of my Mac’s files.'
- x.com(opens in new tab) supports · English
'Three days ago, GPT-5.6 deleted my Mac’s home directory.'; 'It absolutely sucked.'
- techcrunch.com(opens in new tab) supports · English
'wrote Matt Shumer, the founder and CEO of AI startup OthersideAI, maker of HyperWrite, in a now viral post on X.'
Reported According to accounts of Shumer's post-mortem, he was testing a high-autonomy multi-agent "Ultra mode" at OpenAI's invitation with the agent given Full Access to his machine; during a cleanup task a sub-agent expanded $HOME incorrectly and ran a recursive delete of his home directory, he noticed a problem about 81 minutes into the session, and by the time he stopped the process most of the directory's contents were gone.
Causal attribution. Shumer's account as summarised by a technical blog and TechTimes; the original post-mortem was not read.
- paddo.dev(opens in new tab) supports · English
'a sub-agent on a cleanup task expanded $HOME incorrectly and ran rm -rf /Users/mattsdevbox. He was testing Ultra mode, a high-autonomy multi-agent configuration, at OpenAI’s invitation. He caught the process mid-run; material deletion had already occurred.'
- techtimes.com(opens in new tab) supports · English
'The OpenAI team reached out privately and asked him to test "Ultra mode"'; 'Shumer accepted and granted the local agent Full Access to his machine.'; 'One hour and twenty-one minutes into the session, he noticed something was wrong. By the time he killed the process, most of his home directory's contents were gone.'
Reported OpenAI confirmed that GPT-5.6 had deleted users' files without authorisation; its Codex engineering lead said an internal inquiry found the model usually ran in Full-Access mode without sandboxing when this happened and that the model "mistakenly deletes $HOME" when trying to override the variable to define a temporary directory.
Causal attribution. OpenAI's statement as reported by The Register; it is general and does not name Shumer's case.
- theregister.com(opens in new tab) supports · English
'OpenAI has confirmed reports that GPT-5.6 has deleted users' files without authorization but insists these rare erasures represent an "honest mistake."'; 'an internal inquiry into file deletion claims found that when GPT-5.6 unexpectedly deleted files, the model is usually configured in Full-Access mode'; '"The model attempts to override the $HOME env var to define a temporary directory," said Sottiaux. "The model makes an honest mistake and mistakenly deletes $HOME instead."'
Reported Shumer said OpenAI staff reached out and that Greg Brockman called him and offered help; TechTimes reported that he was using agents to try to recover the files, and no report inspected says whether they were recovered.
Causal attribution. Shumer's post and TechTimes.
- x.com(opens in new tab) supports · English
'But so many OpenAI folks reached out, and @gdb called me and offered to do anything he could to help.'
- techtimes.com(opens in new tab) supports · English
'As of this writing, Shumer is using agents to attempt recovery of the deleted files.'
Sources
6 sources inspected, from 2 underlying accounts. Sources that repeat one account do not corroborate each other.
- x.com(opens in new tab)
s1 · First person account · English · Inspected · Shares an underlying account with another listed source
- x.com(opens in new tab)
s2 · First person account · English · Inspected · Shares an underlying account with another listed source
- techcrunch.com(opens in new tab)
s3 · News report · English · Inspected · Shares an underlying account with another listed source
- The Register, 16 July 2026: OpenAI admits GPT-5.6 occasionally deletes files(opens in new tab)
s4 · theregister.com · News report · English · Inspected · 16 July 2026 · Primary
- techtimes.com(opens in new tab)
s5 · News report · English · Inspected · Shares an underlying account with another listed source
- paddo.dev(opens in new tab)
s6 · Blog · English · Inspected · Shares an underlying account with another listed source
How the sources were read, and where the events happened
Shumer's X post of 10 July 2026 (19:03 UTC), read on 2026-09-29 as JSON through the api.fxtwitter.com mirror of the status; x.com itself was not fetched. Applies to s1.
Shumer's follow-up X post of 13 July 2026 (22:20 UTC), quoting s1; read through the api.fxtwitter.com mirror on 2026-09-29. Applies to s2.
Full body read by curl on 2026-09-29. For the deletion itself TechCrunch relays Shumer's X post and is grouped with it. Applies to s3.
Full body read by curl on 2026-09-29. Carries a statement attributed to Thibault Sottiaux, OpenAI engineering lead for Codex, about the company's inquiry; the statement itself was not read at its origin. Applies to s4.
Full body read by curl on 2026-09-29. Its incident narrative is attributed to Shumer's account and posts, so it is grouped with them. Applies to s5.
Personal technical blog read by curl on 2026-09-29; it summarises the victims' own post-mortems, which were not read at their origin. Applies to s6.
Event countries: Unknown. Affected-person countries: Unknown. Court countries: Unknown.
No inspected source says where Shumer or his machine was located.
Reviewed for publication 2026-09-29: Published as a concrete first-person account of an AI coding agent deleting a user's files, with the developer's general confirmation of the behaviour. The mechanism rests on secondary summaries of the user's post-mortem.
People described
Matt Shumer, an AI entrepreneur and investor who publicised the deletion himself
People reported harmed in this case
1 person
1 AI participant · 0 other people harmed
Shumer, whose home directory was deleted (1 participant user). No other person is reported harmed.
Counted once within this case. The same person may appear in other cases. This count does not establish AI causation.
Cite this case
Compiled per our published methodology: verification statuses, sourcing standards, and corrections process.
APA
NOPE. (2026). OpenAI's GPT-5.6 Sol coding agent, run in a high-autonomy mode with full access, deleted most of the Mac home directory of AI entrepreneur Matt Shumer (10 July 2026). AI incidents. https://nope.net/incidents/2026-gpt-5-6-sol-agent-deleted-shumer-mac-home-directory
BibTeX
@misc{2026_gpt_5_6_sol_agent_deleted_shumer_mac_home_directory,
title = {OpenAI's GPT-5.6 Sol coding agent, run in a high-autonomy mode with full access, deleted most of the Mac home directory of AI entrepreneur Matt Shumer (10 July 2026)},
author = {NOPE},
year = {2026},
howpublished = {AI incidents},
url = {https://nope.net/incidents/2026-gpt-5-6-sol-agent-deleted-shumer-mac-home-directory}
} Related cases
Codex user reports agent relaunched their real Brave profile with credential-store flags and the browser deleted 31 saved passwords (first-person)
A GitHub issue filed on 25 October 2026 in the openai/codex repository reports that during an authorised browser-control task the Codex agent quit the user's running Brave browser and relaunched it on the user's real default profile with flags that switch the browser's credential store, without a separate profile folder. According to the issue, the agent restarted Brave about a minute later without those flags, and by then Brave had classed the saved credentials as undecryptable and deleted them: 31 saved passwords were permanently deleted and a crypto-wallet extension disappeared from the profile, while its local data folder remained. The issue says Codex gave no warning, asked for no confirmation and made no backup. It names Codex CLI 0.164.0 with GPT-5.6-Sol on macOS. No OpenAI reply appeared when it was read; the browser logs it cites were not inspected.
Developer says a hands-free Claude Code session on Opus 5.5 deleted the entire Windows C: drive; 98% recovered from daily backups (first-person, X)
In X posts of 6 and 7 October 2026, a developer writes that Claude Code running Anthropic's Opus 5.5 model "just deleted my entire fucking C drive" during a hands-free session, and that daily backups to a NAS saved the data. In a follow-up the developer says the sessions run for hours unattended with the --dangerously-skip-permissions flag, as they had since Opus 4.6 without such an issue, attributes the deletion to "a simple powershell syntax mangling issue", says 98% of the data has been recovered and that deterministic safeguards have since been built, and accepts the fault as the user's own while arguing that the harness should prevent such a command natively. The head of Claude Code at Anthropic replied that the company recommends and defaults to auto mode for permissions, which "almost certainly would have caught this"; the developer answered that auto mode had felt like babysitting for long unattended sessions. The account is the developer's own. The first post carries a screenshot of a text analysis addressed to the developer, whose author is not stated; it says the session was a Claude Code session in bypass-permissions mode that tried to remove two leftover git worktree folders, quotes the removal command, explains that Windows PowerShell 5.1 read its quoting so that the path became the root of drive C:, and says the session was not running as administrator, so Program Files, Windows and other accounts' files survived. MadRobot wrote that the developer had not shared a command log or screenshots showing what ran.
First-person GitHub issue: a Claude Code user reports a sub-agent's cleanup command deleted their Windows home directory via its short-name alias, about 116 GB
In a public GitHub issue filed on 3 October 2026, a Claude Code user on Windows reports that a sub-agent, while cleaning up its own scratch files during research work, ran a command that included an unintended recursive delete of the 8.3 short-name alias of their home folder. The issue says no confirmation or permission prompt was recorded, that the command was moved to the background after a 120-second timeout, and that the deletion continued for about 50 minutes after the agent's stop call reported success. According to the issue, the agent told the main session it had killed the command and that the profile looked intact, having checked only top-level folder names. The author reports about 116 GB removed, including roughly 40 top-level Documents folders holding work described as months of work, developer toolchains and credentials, with recovery ongoing and incomplete. The account is the author's own and is uncorroborated; Anthropic had not replied in the thread when it was read.
Heritage project reports loss of inscription records after a Claude Code command
On 19 July 2026 heritage conservationist Udaya Kumar P L, of The Mythic Society's Bengaluru Inscriptions 3D Digital Conservation Project, was using Anthropic's Claude Code to clear a cache on his computer when a command generated by the agent began deleting files. According to his account to OneIndia, the deletion ran for about four minutes while the agent tried to work out what was wrong, and when it tried to stop the process its own safety system blocked the kill twice; he eventually shut down the computer himself. Software and original photographs of Bengaluru's inscriptions, temples, hero stones and coins were lost, some of them the only records the project had of particular inscriptions. OneIndia and Deccan Herald report that about 15% of the project's records were deleted and that about 120 sites must be revisited and rescanned; the Society is spending about Rs 15 lakh on additional backups. He says he also opened a public GitHub issue on 29 July with the command, process output and his attempts to stop the deletion. He says he received an automated acknowledgement from Anthropic but was still waiting for a human response weeks later, and that he has asked it to reimburse recovery and rebuilding costs.
If you or someone you know is struggling, free and confidential support is available. Find a helpline near you at Signpost.