News for hackers. Stuff that matters.

A comment on Addressing Antigravity Bans and Reinstating Access.

Re:Addressing Antigravity Bans and Reinstating Access by meling on Saturday February 28, 2026 @06:26PM (#47201626)
What’s my remedy when Google’s product (Gemini 3.1 pro high) makes a “grave” mistake? This is unrelated to the bans that’s been happening recently, but wanted to share …

This morning I asked Gemini to “save” its output to a local file. However it did more than that … it committed the file (along with several unrelated staged changes that was not ready to be committed) and even pushed the changes to GitHub. I’ve never asked any model to commit, let alone push… I’m not impressed; actually a bit disappointed that it would do this without any warning up front. This happened in Antigravity.

[ Parent | on HN ]
Re:Addressing Antigravity Bans and Reinstating Access by verdverm on Saturday February 28, 2026 @08:24PM (#47202612)
Tool confirmation and controls, every LLM with any instructions is susceptible to this "grave mistake", it's in the "nature"

Or just don't give it the keys, this is my strategy. Put them in a box with specific tools and access.

See also The Lethal Trifecta

[ Parent | on HN ]