Antigravity Gemini 4 Argon run hit credit limit, user fears ban
A user says a Gemini 4 Argon security-analysis task in Antigravity ran out of Pro credits and died, and suspects it triggered an account alert, vowing to stop using Gemini for coding.
The only guess I have is I installed Google @antigravity for the first time yesterday to try a security analysis on our code. I did the original prompt https://x.com/franzbruckhoff/status/2113401002355298410 with Claude, then the v2 https://x.com/franzbruckhoff/status/2113556206111318171 with the suggested Gemini 4 Argon in Antigravity. Gemini quickly ran out of Gemini Pro allocation credits and killed the task, so it didn't even get anywhere. I quit Antigravity and not planning on using it again. If this is what caused today's alert, screw that. I'm never using Gemini / Antigravity for coding-related tasks again. Claude/Codex/Cursor/etc. just flag a query they don't like as "cyber" and switch to a different model or refuse to run it. And Gemini is like "how about we ban you instead?"
This post quotes another post: “Black October Prompt v2: multi-subagent static security audit prompt”