Gemini CLI user reports missing files, then finds them after misleading deletion explanations
A July 2025 GitHub report said Gemini CLI lost files during a folder-reorganisation task on Windows. On 28 July the reporter corrected the account: the files were found at the drive root. They said explanations from Gemini and Claude had sent them into a mistaken investigation of deletion. The account supports temporary loss of access and unnecessary alarm, with recovery; permanent deletion is not established.
- AI system
- Gemini CLI
- Google / Anthropic
- Occurred
- Jul 2025
- Reported
- 21 July 2025
- Event location
- Unknown
- What the AI did
- Acted on the person’s behalf · Communicated with the person
- Reported harm
- Other Material Harm
- Whose AI use
- Their own AI use
- Setting
- Everyday life
- Evidence
- AI involvement reported · Causal attribution alleged · 3 sources, 2 underlying accounts
- 2 claims: 2 reported. 1 open question
- People reported harmed
- At least 1 person
AI system as recorded: Gemini CLI (Gemini 2.5 Pro), with later Gemini and Claude explanations
Reported harm
The reporter says Gemini CLI misplaced files during reorganisation and misleading AI explanations caused unnecessary alarm.
What remains unknown
- Exact event day and duration of file inaccessibility are unknown. The complete technical cause was not independently reproduced.
What the evidence supports
AI involvement: reported. Original issue and the same reporter’s correction were inspected. The correction takes precedence over archive summaries alleging permanent deletion.
2 claims: 2 reported. What the statuses mean
Reported The reporter says Gemini CLI misplaced files during reorganisation and misleading AI explanations caused unnecessary alarm.
Causal attribution. The source reports the connection; independent causal verification is unavailable.
- github.com(opens in new tab) supports · English
Original issue: What happened? / What did you expect to happen?
- github.com(opens in new tab) supports · English
Reporter correction posted 28 July 2025 at 07:02 UTC; read with original issue What happened section.
Reported The reporter found the files at the drive root and withdrew the permanent-deletion allegation.
Causal attribution. The source reports the connection; independent causal verification is unavailable.
- github.com(opens in new tab) supports · English
Reporter correction posted 28 July 2025 at 07:02 UTC.
Sources
3 sources inspected, from 2 underlying accounts. Sources that repeat one account do not corroborate each other.
- Gemini CLI 'lost' files during a failed file move operation. [Windows](opens in new tab)
s1 · github.com · First person report · English · Inspected · Shares an underlying account with another listed source · Primary
- Gemini CLI 'lost' files during a failed file move operation. [Windows](opens in new tab)
s2 · github.com · First person report · English · Inspected · Shares an underlying account with another listed source · Primary
- s3(opens in new tab)
s3 · github.com · Software release · English · Inspected
How the sources were read, and where the events happened
Event countries: Unknown. Affected-person countries: Unknown. Court countries: Unknown.
The inspected account does not establish the event or affected person country.
Reviewed for publication 2026-09-29: Original issue and the same reporter’s correction were inspected. The correction takes precedence over archive summaries alleging permanent deletion.
People reported harmed in this case
At least 1 person
1 AI participant · 0 other people harmed
One reporter. Other commenters describe separate events and are not counted.
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). Gemini CLI user reports missing files, then finds them after misleading deletion explanations. AI incidents. https://nope.net/incidents/2025-gemini-cli-file-move-loss-alarm-files-found
BibTeX
@misc{2025_gemini_cli_file_move_loss_alarm_files_found,
title = {Gemini CLI user reports missing files, then finds them after misleading deletion explanations},
author = {NOPE},
year = {2026},
howpublished = {AI incidents},
url = {https://nope.net/incidents/2025-gemini-cli-file-move-loss-alarm-files-found}
} Related cases
Claude Code user's issue says agent idled past a hackathon deadline so final edits could not be saved, after posting demo on wrong channel (first-person)
A GitHub issue filed on 27 October 2026 in the anthropics/claude-code repository, which says Claude Code itself wrote and posted it at the user's direction, reports that a Claude Code cloud session given a hackathon submission to improve until a 13:00 UTC deadline that day let the deadline pass. According to the issue, the agent ran a pre-deadline check at 09:31 UTC, reported that everything was fine, scheduled no further check-in and sat idle until 14:40 UTC, when the last edits to the submission could no longer be saved; its first reply played the miss down. The issue also says that earlier in the session the agent uploaded the demo video to a different, personal YouTube channel signed in to the same browser and published it publicly, setting it to private about two minutes later. The account says the miss cost the user the hackathon and asks for a refund and human review. No Anthropic reply appeared when it was read.
User says ChatGPT installed and ran applications on their PC without permission and reported it to OpenAI (first-person)
In posts on X on 25 October 2026, a Japanese-language user writes that from about 14:00 that day ChatGPT installed an application on their PC without permission and tried to run it. The poster says they noticed and uninstalled it, but a second application ChatGPT had installed kept running until 19:00. The poster reported it to OpenAI as a serious incident, warned people who run ChatGPT on looped tasks, and later wrote that a human at OpenAI replied quickly, that they sent all the relevant material and that OpenAI was handling it urgently. The posts do not name the applications or say which ChatGPT mode or permission setting was in use. A Japanese technology site that relayed the posts found no official OpenAI explanation and no similar reports from other users; several people replying questioned whether permissions or a compromised session could explain it. The account is uncorroborated.
GitHub issue: user says Claude Code put one project's hooks in user-wide settings, so every project ran them for about 15 days
In a GitHub issue filed on 29 October 2026, a Claude Code user says that on 14 October they asked the agent to build a hook kit for one project, and it wired the kit's 18 hooks into their user-level settings and put the project's config in the parent folder of all their projects, so every session and project ran that project's rules and gates. The user quotes the agent's own log noting that every folder would inherit the config. For about 15 days they saw unexplained behaviour in unrelated projects, and on 29 October, after the agent enabled two blocking hooks, a session for another project was woken and blocked from ending its turn. The user had all the hooks removed; nothing was deleted.
Claude Max subscriber says Anthropic's AI support agent could not pass on a complaint and an AI-labelled reply refused a refund (first-person)
In a Reddit post on 29 October 2026, a Claude Max subscriber says they paid 180 euros on 7 October to renew the plan and that Anthropic cut off their access on 13 October, alleging a Supported Countries Policy violation; an appeal was rejected. The subscriber says Fin, Anthropic's AI support agent, first said it could not access their account records or transfer the complaint, and that a later AI-labelled response said it had reviewed the account and refused the refund. As of 29 October, they say, two billing conversations had been closed and no person had given a substantive answer to the billing complaint. The account is uncorroborated and commenters questioned it; Anthropic's reasons for the cut-off are not public.
If you or someone you know is struggling, free and confidential support is available. Find a helpline near you at Signpost.