Gemini CLI will stop working from June 18, 2026
71–80 of 224 posts
Re: Gemini CLI will stop working from June 18, 2026
#72Even if there are competing implementations, in terms of brand recognition, I feel like “Gemini” is more closely associated with Google than “Antigravity”. Why pick the more obscure option?!
Perhaps they felt the sentiment on Gemini CLI was beyond repair, but surely there must be some voice on the inside saying “developers will never adopt our products if we keep killing them”.
Re: Gemini CLI will stop working from June 18, 2026
#73I would love to sign up for antigravity cli but when I click on Get Plan it says: “This account isn't eligible for Google Antigravity benefits included with Google AI plans Google Antigravity benefits included with Google AI plans aren't available in some countries or for people under a certain age. Learn more about Google One feature eligibility.” With a button that says “Explore Google AI Plans” that when I click o…
This is the main reason I’m not using Gemini for work. Google won’t let me pay for it. I pay for just about every AI service under the sun but Google needs to refuse my card, account, location or a combination of these. But they happily take my money for a couple of Workspce accounts.
Re: Gemini CLI will stop working from June 18, 2026
#74Earlier quoted context omitted.
What if their telemetry shows very low usage? I've seen virtually no discussion of Gemini CLI online.
There are 13,700 forks of its repo on Github. If anything, I suspect closing the source for their coding agent may have been part of the goal.
Re: Gemini CLI will stop working from June 18, 2026
#75As luck would have it, I tried Antigravity for the first time a few days ago. It was a complete buggy mess - at one point I asked Gemini why it could not use the network despite having network access enabled in the sandbox settings, and it told me that although it had network access, it couldn't use mdnsresponder while running with the built-in sandbox. Like, how well thought out, network access without DNS. After bu…
What I've done instead is built a script to create a disposable virtual machine (using incus to manage it).
And then I just run the CLI inside the virtual machine and delete the vm at the end of each day.
Re: Gemini CLI will stop working from June 18, 2026
#76Re: Gemini CLI will stop working from June 18, 2026
#77Whoever is in charge of these decisions, is absolutely disconnected with the reality. First they sent a message saying the Ultra plan is ending, with no other option for a Workspace use to buy an equivalent plan. It was suppose to be active tilll June or July 7 , that's all. So the users are not suppose to know how they will need to plan or budget and just guess. I read once that after a certain level , the managers…
Re: Gemini CLI will stop working from June 18, 2026
#78Earlier quoted context omitted.
100%. I really wish that I could treat them as a valid option, but they continuously reaffirm the position that it is dangerous to rely on them for anything commercial.
I feel a strange sense of relief that Google’s models are currently not industry leading and I don’t need to worry about not using them.
Re: Gemini CLI will stop working from June 18, 2026
#79Earlier quoted context omitted.
What if their telemetry shows very low usage? I've seen virtually no discussion of Gemini CLI online.
There are 13,700 forks of its repo on Github. If anything, I suspect closing the source for their coding agent may have been part of the goal.
Re: Gemini CLI will stop working from June 18, 2026
#80This is the right move but I don’t know if I am ready to try them again. I am still bitter from the significantly reduced quotas, even on Ultra, their highest tier. Claude became unusable for me. It would be much better if they just gave up on Gemini for coding and exclusively adopted Claude models. Even Deep Mind folks themselves prefer Claude over Gemini[1]. [1]: https://www.businessinsider.com/google-deepmind-ai-t…