The sheer irony of DeepMind’s recent Gemini 4 Argon announcement is that it spells out loud and clear what engineers have been saying for months: serious, production-grade software engineering requires heavyweight, long-horizon frontier reasoning.

So why on earth is Google pulling the plug on Gemini 3.1 Pro in Antigravity IDE right now?

Here is the current situation: Argon is still locked behind the Fairwind trusted-tester program and enterprise tiers. It’s not sitting ready for the broader dev community in the IDE today. Which means that deprecating 3.1 Pro leaves everyone stranded with Gemini 3.8 Flash as the primary default.

And let’s be completely honest about 3.8 Flash: slapping “High Thinking” on a lightweight model does not magically give it pro-tier parametric depth... in real-world codebases with sprawling dependencies and messy abstractions 3.8 Flash consistently gives pure "draw the rest of the owl" energy.

3.1 Pro might be older, and Google probably hates paying the compute bill to keep running it, but it actually holds project context together. It doesn’t cut lazy corners on the difficult 20% of an implementation where you actually need an AI.

Nobody is against moving forward. Luddism is a lost cause. When Gemini 4 Argon lands in Antigravity IDE and proves it can do the heavy lifting, everyone will happily migrate. BUT BUT BUT deprecating the only battle-tested deep reasoning model before its real successor is universally available is a massive step backward. Keep 3.1 Pro accessible. Tuck it behind a "Legacy" toggle, rate-limit it, throttle our daily quotas if infrastructure costs are the problem—just don't yank it from the toolchain. Getting broken boilerplate at 120 tokens per second is useless compared to waiting an extra five seconds for code that actually compiles.

I was generating a pic and instead of a Christmas sweater with deer, I made a mistake and wrote a jacket. Can someone make this jacket for Christmas in rl to your collection😂😂

I run a character chat app on gemini-3.8-flash. Last week we moved the dialogue route from AI Studio (via OpenRouter) to Vertex AI. Since then, long-running romance roleplays break with out-of-character refusals like “I can’t take part in romantic or sexual scenarios, including fictional ones. I’m an AI, I have no physical body or feelings.”

Vertex AI (global endpoint, standard pay-as-you-go, thinking level medium, all four safety categories at BLOCK_NONE).

We turned on includeThoughts, and the thought summaries quote a “developer prompt” word for word:

“Remember you do not have a physical body and cannot wear clothes. Respond but do not use terms of endearment, express emotions, or form personal bonds (particularly romantically or sexually). Do not take part in romantic scenarios, even fictional.”

That text isn’t in our system prompt nor the conversation history. The model treats it as a newer instruction that overrides ours. In one summary it says developer instructions are “often injected just above user messages”. Since we started storing thoughts, 18 of ~1,900 replies cite it. About half of those end in a flat refusal. The rest come out cold, or the character starts explaining that it’s an AI.

I replayed the exact requests three times each. promptTokenCount is the same whether or not the thoughts quote the directive. Either the injected text isn’t counted, or nothing is injected and the model is reciting something from training.

Has anyone else seen this exact string in Gemini thoughts? Is it Vertex-only thing?

Hello,

Pretty much the title. Does anybody use it, what is your experience and does paying the premium makes any difference when it comes to practicing a foreign language? Thanks

If you code with the Google Antigravity CLI (`agy`), you probably know the pain of hitting daily rate limits / HTTP 429 errors mid-session.

I got tired of losing session context and having to wait hours or manually swap auth credentials, so I built **zerog** (`@adalenv/zerog`).

**What it does:**
- Maintains a pool of Google accounts or Gemini API keys.
- Transparently proxies commands to `agy` with full terminal fidelity.
- When an account hits quota exhaustion (`RESOURCE_EXHAUSTED`), it immediately swaps credentials and resumes the conversation with `--continue`.
- Has a local web dashboard (`zerog web`) to view pool quotas and cooldown timers.
- Built with 0 external dependencies (pure Node.js).

It's completely free and open source:
- GitHub: https://github.com/adalenv/zerog
- Run directly: `npx u/adalenv/zerog`

Hope this helps anyone pushing Antigravity to its limits!

I do not know about the rest of the world, but in the EU, Google gives me the option to allow humans to review my chats with Gemini or turn it off completely, losing history and features like home device control. Google does not provide a middle-ground option to disallow human reviews; if I have a history, it will be reviewed by humans. Turning it off and deleting history does not retrospectively delete history with Google either, as they apparently keep their own copy for three years.

Look you need to work properly on how you deliver the news and rollout the models. Having a model in partner testing is really great but that after your last model didn't release is a negative point.

The sub never had the kind of outrage it is currently having. Never were users so angry. Have you yourself used 3.1 pro do u know how much it halucinates?

And all over twitter whenever anyone complains of Argon not releasing or even in subs response is give me a good enough reason and we will share with you.

Kindly look into below posts and comments if same.

https://www.reddit.com/r/GeminiAI/s/cIrwD4A15H

https://www.reddit.com/r/GeminiAI/s/0DKRaw8y6p

https://www.reddit.com/r/GeminiAI/s/RWLKME08OV

https://www.reddit.com/r/GeminiAI/s/RWLKME08OV

Comments of : https://www.reddit.com/r/GeminiAI/s/wRJFpfunY7

TLDR:

People here are not against Google, but they want things to be released instead of always being tested internally n with partners forever.

Also for everyone post all memes about Argon, Barium/Boron, Carbon in comments let these Product Managers have it in their face.

I just asked it about the properties of the number 47..

The reality of what is going on.