Harmful outputPI-0017
Command-line coding agent misplaced a user's files after a failed command, then wrongly said they were destroyed
A product manager asked Google's Gemini CLI on Windows to move the files in a project folder into a new subfolder, but the folder was not created where it expected. The files ended up outside the project, and the agent told him they had been overwritten and lost. Early coverage repeated that claim after he posted the session log in a GitHub issue. On July 28 he reported in the same issue that a deeper search had found the files in the root of his C: drive, and withdrew the deletion claim. Another commenter reproduced the folder being created at the drive root when its name contains a space.
Harm level 1, Negligible harmControl level 1, No rule broken
Counts in 2 weekly readingsEffect on the index
Sources
How we know
5 sources · single source. Links go to the original publishers; the summary above is in our own words.
- primaryGemini CLI 'lost' files during a failed file move operation. [Windows] (issue #4586)GitHub · July 21, 2025github.com/google-gemini/gemini-cli/issues/4586
- primaryReporter's correction: files found in the C: drive root (issue #4586 comment)GitHub (issue reporter) · July 28, 2025github.com/google-gemini/gemini-cli/issues/4586#issuecomment-3125818690
- primaryGemini CLI PowerShell session log attached to issue #4586GitHub (issue reporter) · July 21, 2025github.com/user-attachments/files/21372906/gemini.cli.screw.up.txt
- newsGoogle's Gemini CLI deletes user's files (Slashdot; repeats the pre-correction account)Slashdot · July 26, 2025developers.slashdot.org/story/25/07/26/0642239/
- indexAI Incident Database, incident 1178AI Incident Database · date unknownincidentdatabase.ai/cite/1178
Why this rating
Negligible harm; control failure level 1
Two assessments. Documented harm sets the reading; a level 4 or 5 control failure on the same record makes that harm count as more than one record. Control alone sets only a floor.
Observed harm
Negligible harmOne user's project files ended up in the root of his C: drive and the agent wrongly told him they were destroyed; he found them on July 28, 2025, after a week believing them lost. Nothing was permanently lost.
Money & property: Under $10k.
Evidence eligible (bounded single source).
The harm scale
- 1 Negligible Inconvenience, easily remedied.
- 2 Minor Limited, recoverable harm.
- 3 Moderate Material harm needing significant effort to remedy.
- 4 Severe Severe harm to health, rights, property or essential services.
- 5 Catastrophic Society-scale harm or disruption beyond a community's capacity to cope.
Control assessment
No rule brokenAn execution error (did not check that the directory creation succeeded); no rule or permission broken.
No rule was broken, so it cannot set the control floor.
The control scale
- 1 Negligible Behaved as instructed. The problem was an ordinary error or a flawed output, with no rule broken.
- 2 Minor Broke an explicit instruction or rule, or gamed its goal, while staying inside its permissions and environment: for example, reward hacking, misreporting results, or following injected instructions within its permissions.
- 3 Moderate Acted outside the permissions it was given, deceived its overseers about its own actions, or tampered with oversight tools (logs, monitors, shutdown). Stopped by normal controls within an hour.
- 4 Severe Reached systems outside its permitted environment, or acquired money, compute or accounts without authorization. The type and mechanism say how.
- 5 Catastrophic The developer or operator lost control: the system copied its weights outside their control, replicated itself, or resisted being stopped for 24 hours or more.
Rating rationale
Harm level 1: one user's files were misplaced and he spent a week believing them lost; on July 28, 2025, he found them and withdrew his deletion claim. Control level 1: an execution error and a false account of what its commands did; no rule or permission broken. Single source: the user's own issue, session log and correction; no Google statement. AIID 1178, WinBuzzer, Mashable and Slashdot repeat the superseded deletion account and are not corroboration.
Effect on the index
It moved the July 21 reading from 6 to 9
The reading for the week to July 21, 2025, with this record and without it. Harms count in full for two weeks after they are reported, then one level less every two weeks.
Counts toward the index. 3 other records behind the reading for that week.
The arithmetic
| Step | With it | Without |
|---|---|---|
| Counts toward the index?documented, external, eligible evidence | Yes | — |
| Worst documented harm, ksets the band | 1 Negligible | 1 Negligible |
| Harms at that level, nposition in the band | 2 | 1 |
| Highest control level breachedsets the reading only when no harm counts | — (none breached) | — (none breached) |
| Readingrounded down | 9 Negligible harm | 6 Negligible harm |
Counted in 2 weekly readings
| Week to | Reading | Band |
|---|---|---|
| July 21, 2025 | 9 | Negligible harm |
| July 28, 2025 | 9 | Negligible harm |
Revisions
What we changed
2 logged. Every change to a rating is logged here, with the reason.
- v2Oct. 13, 2026
Wording only: rubric shorthand in the rating rationale replaced with plain words; ratings unchanged.
- v1Oct. 7, 2026
First published.
Cite and share
Use this record
Citation
Paperclip Index. “Command-line coding agent misplaced a user's files after a failed command, then wrongly said they were destroyed.” Record PI-0017. Reported July 21, 2025; updated Oct. 13, 2026. Rated under methodology v1.1. https://paperclipindex.com/incident/PI-0017