The only reason to do this is to save usage on the subscription. but because the value for money is so terrible in antigravity, you’re better off just using Claude Opus or GPT Sol for everything.
I’m glad Google is kinda back, but today there’s no reason to code with Gemini.
FWIW I've found the complete opposite to be true, and have gone claude->chatgpt->gemini over the past few months.
Why?
Re:Gemini 4 Hydrogen and Orchestrator
by engineer_22 on Thursday November 12, 2026 @03:51PM
(#50474087)
Im slowly migrating more of my work to Gemini too, Gemini is a workhorse now, 1M context is huge and their reasoning took a huge leap with Argon. I'm not in software, I'm in physical engineering, and where Claude is unpredictable w.r.t. engineering risk, Gemini is steady, measured. That's been my perception, anyway.
I set up my subagents with specific models based on how complex I believe the problem space is. I'm nervous to delegate that authority to a model (since models tend to be... optimistic about their capabilities.)
That said, not every coding task is a difficult coding task. Plenty are boilerplate, plumbing, or simple test authoring that could use a flash model, so maybe this would downgrade nicely.
On the other hand, it's trivial for me to set up some guidelines to create different subagents for different task domains, and just pin those models to those tasks -- implementor (hard) and implementor (easy) or whatever.