Comment by whywhywhywhy
1 month ago
> which made the command hunt for the word match ending space which was regrettably, the D:\
Is this even how the delete command would work in that situation?
>rmdir /s /q D:\ETSY 2025\Antigravity Projects\Image Selector\client\node_modules.vite
like wouldn't it just say "Folder D:\ETSY not found" rather than delete the parent folder
LLM there generates fake analysis for cynically simulated compliance. The reality is that it was told to run commands and just made a mistake. Dude guilt trips the AI by asking about permission.
> The reality is that it was told to run commands and just made a mistake.
The mistake is that the user gave an LLM access to the rmdir command on a drive with important data on it and either didn't look at the rmdir command before it was executed to see what it would do, or did look at it and didn't understand what it was going to do.
Most dramatic stories on Reddit should be taken with a pinch of salt at least... LLM deleting a drive and the user just calmly asking it about that - maybe a lot more.
It probably wasn't the rmdir command that deleted the parent folder by itself, but the LLM did the traversal. The LLM probably did this:
Detected that it failed, then the LLM issued the traversal command
And so on...
And then that failed, so...
I would like to know the same thing. Can someone please confirm this?
Running this command in cmd attempts to delete (I ran without /q to check):
Z:\ETSY (-> Deletes if it exists.)
"2025\Antigravity" (-> The system cannot find the path specified.)
"Projects\Image" (-> The system cannot find the path specified.)
"Selector\client\node_modules.vite" (-> The system cannot find the path specified.)
It does not delete the Z:\ drive.