Gemini CLI will stop working from June 18, 2026
developers.googleblog.com
Gemini CLI will stop working from June 18, 2026
1–10 of 224 posts
Re: Gemini CLI will stop working from June 18, 2026
#2And Antigravity CLI starts working from today, interesting
Re: Gemini CLI will stop working from June 18, 2026
#3Yeah, so they are worried about things like CAS that let you use lots of CLI agents from different companies. The fork I'm using lets me use Claude and Codex, and Gemini if I want, but I haven't much lately. Anyway, that sounds like what's happening. Is that wrong?
Re: Gemini CLI will stop working from June 18, 2026
#4This is so confusing. So what happens to Gemini Code Assist plans?
What do the Antigravity quotas mean per plan?
Re: Gemini CLI will stop working from June 18, 2026
#5Say goodbye to metered usage via API keys you control, and hello to opaque pricing and usage limits.
Re: Gemini CLI will stop working from June 18, 2026
#6Welcome to the Google graveyard, Gemini CLI.
Not that it will be missed much. Using it was the worst experience out of any harness.
Re: Gemini CLI will stop working from June 18, 2026
#7Stop working? It never even started working for me, I tried it and always just got errors or lack of quota.
Re: Gemini CLI will stop working from June 18, 2026
#8Google really can’t help themselves but to have some internal re-org kill off a public thing people are actively using. It’s honestly impressive how consistent they are.
Re: Gemini CLI will stop working from June 18, 2026
#9I read through the docs. There is no mention of whether programmatic usage or Agent Client Protocol will continue be supported in Antigravity CLI.
Re: Gemini CLI will stop working from June 18, 2026
#10Yeah, so they are worried about things like CAS that let you use lots of CLI agents from different companies. The fork I'm using lets me use Claude and Codex, and Gemini if I want, but I haven't much lately. Anyway, that sounds like what's happening. Is that wrong?
I think we will need to move to workarounds based on MCP going forwards.
> run CLI agent with an initial prompt
> tell the agent it isn't allowed to directly reply to the user and must use your tool instead. also all of the CLI's original interactive tools are blocked and it has to use your alternatives
> when the agent uses tools in the MCP, it redirects to your GUI's prompt editor