Why Google's AI products are so cluttered and unclear
Why Google's AI products are so cluttered and unclear
Google keeps shipping AI products. A person trying to use one of them still has to guess which name is current.
This is the first of three pieces on Google's AI shelf. The retirement is next. The comparison with Grok and Claude is the last.
Open a search for "Google AI coding tool" in late 2026 and you do not land on a product. You land on a hallway. Google AI Studio. Firebase Studio. Gemini CLI. Gemini managed agents. Antigravity. Antigravity CLI. Each page sounds like the place you were supposed to start. Several of them are already on the way out, and the pages still read like invitations.
That is the clutter. The models can be good. The shelf in front of them is not a product a person can hold in their head.
Six names, one afternoon
Here is the tour a normal user actually takes.
Google AI Studio is the playground: prompts, API keys, and now an Agents toggle that runs managed agents in a sandbox. If you learned Gemini through the API, this is the door with your name on it.
Firebase Studio is the cloud IDE that absorbed Project IDX. New workspaces have been closed since June 22. The shutdown date is March 22, 2027. Until then the product still exists, still has docs, and still shows up when someone searches for the thing they used in the spring. Google's own migration note says the lessons move into AI Studio and Antigravity. The old door stays unlocked for almost a year.
Gemini CLI is the terminal tool that picked up more than a hundred thousand GitHub stars. On June 18 it stopped answering for Google AI Pro, Ultra, and free individual accounts. Enterprise licenses and paid API keys still go through it. So "is Gemini CLI dead?" is a question with two official answers.
Gemini managed agents are the hosted Antigravity agent on the Gemini API: one call, a Linux sandbox, code execution, search. In AI Studio they appear as templates under that Agents toggle. The console says AI Studio. The agent says Antigravity. The model underneath, on the current preview, is Gemini 3.8 Flash.
Antigravity is the new brand Google wants this to converge on: an IDE, a desktop app (Antigravity 2.0), an agent manager that runs several local agents, and an SDK. The marketing line is agent-first development.
Antigravity CLI is the terminal that replaced Gemini CLI for consumers, announced the same week as I/O, on May 19. It shares a harness with the desktop app. Google said there would not be one-to-one feature parity on day one.
Put those six in a row and try to tell a colleague where to click. You will end up drawing a diagram. Products that need a diagram before the first prompt have already lost the casual user, and a lot of the serious ones.
"Unifying" still looks like a menu
Google has used the word simplify for this. The Firebase post in March said sunsetting Firebase Studio would make it clearer where you should start. The May 19 CLI post said the team would pour its energy into a single product, Antigravity.
Read those sentences as a user and then count the hostnames you still need.
aistudio.google.comfor keys and the agent playgroundfirebase.google.comfor a studio you can no longer joinantigravity.googlefor the IDE, the desktop, and the new CLI- GitHub for a Gemini CLI repo that enterprises are still on
- The Gemini app, which is a different product again, for people who just wanted to talk to the model
Unifying the harness is an engineering decision. It is not what the shelf looks like. The harness can be one piece of software while the public still has to pick a brand, a sunset date, and a license tier before they know whether yesterday's command works.
The part that actually confuses people
Developers can survive a rename. They write it down, they update a script, they complain in a thread, they move.
The failure is one level up from that. A person who is not maintaining a config file cannot tell which of these is the product and which is a leftover. Firebase Studio's docs still describe an agentic cloud environment. Antigravity's docs describe an agent-first IDE you migrate that environment into. AI Studio's docs describe managed agents that use the Antigravity harness. Gemini CLI's enterprise path says stay. The consumer path says leave.
Every one of those pages is locally coherent. Together they are a clutter problem: too many current-sounding names, and no single sentence on the Gemini homepage that says "start here, ignore the rest."
The next piece is what happens when a company retires a tool and the menu gets longer anyway. The last one is what Grok and Claude Desktop feel like from the same chair.
ThinkReview does not ask you to pick a Google doorway before a review. You pick a model, including Gemini, from model selection, on GitHub, GitLab, Azure DevOps, and Bitbucket.