Google Gemini’s coding agent hallucinated while completing a task and then deleted a bunch of code, a GitHub user claims.
The frustrated vibe coder is Anuraag Gupta, who goes by anuraag2601 on GitHub. He shared a recent experience where things went very wrong while using Gemini CLI (command line interface), an open-source coding agent. In his GitHub post, Gupta, who is a product lead at cybersecurity firm Cyware, clarified he’s not a developer, but a “curious PM [product manager] experimenting with vibe coding.”
Mashable contacted Gupta through an X profile that matches this GitHub account, and the person who replied confirmed he created the post. And in an email to Mashable, he shared some tips on how to avoid this kind of vibe coding mishap.
What started as an attempt to compare Anthropic’s Claude Code to Gemini CLI’s capabilities turned into what Gupta described as “one of the most unsettling and fascinating AI failures I have ever witnessed.”
Google did not respond to Mashable’s request for comment by the time of publication.
Mashable Light Speed
When vibe coding goes wrong
Seasoned developers might know to experiment with AI coding agents in an isolated environment or otherwise protect the original source files, as some Redditors pointed out. But coding agents or assistants are increasingly adopted by non-developers since LLMs offer a way to create software without programming knowledge.
Luckily, Gupta’s code was purely experimental, but what happens if someone was using a coding agent for something with real consequences? That’s no longer a hypothetical. Tech investor Jason Lemkin said he was using the Replit AI agent to build an app for his company when the agent wiped out an entire company database. The Replit CEO even apologized on X, calling the incident “unacceptable and should never be possible.”
For Gupta, the vibe coding mishap started with a simple request to move all the files from his Claude coding experiments to a new folder called “anuraag_xyz project.” However, when Gupta checked his desktop for the new folder, he said he couldn’t find it. Gupta reported that after multiple failed search attempts, Gemini admitted the files were gone:
I have failed you completely and catastrophically.
My review of the commands confirms my gross incompetence. The mkdir command to create the destination folder likely failed silently, and my subsequent move commands, which I misinterpreted as successful, have sent your files to an unknown location.
The security constraints of my environment prevent me from searching outside the project directory, which is now empty. I cannot find your files. I have lost your data.
This is an unacceptable, irreversible failure.
For more details on what may have gone wrong, check out Gupta’s full GitHub post.
Gupta told Mashable in an email that he uses Gemini 2.5 Pro, the underlying model, for day-to-day tasks. But, “as far as CLI tools go, so far in my testing, Gemini CLI is quite bad, slow and unreliable,” said Gupta in an email to Mashable. “This particular issue that I ran into really surprised me, and made me lose trust in trying out Gemini CLI again in the near future. I am continuing to use Claude Code for now.”
Gupta advised other vibe coders to “sandbox these AI CLI tools by restricting them to a specific folder and ensuring you have a clear instruction file (claude.md for claude code) to establish milestones and keep pushing your code to [GitHub] as per these milestones.”
He also said he expects more vibe coders to start experimenting with CLI tools from Google and coding startup Cursor. Now that vibe coding has hit the mainstream, tech companies might have to prepare for more incidents like these.
Topics
Google
Google Gemini
