Does Google have a clutter problem with its AI products?

Does Google have a clutter problem with its AI products?
Share

Does Google have a clutter problem with its AI products?

A sunset is supposed to shrink the map. Google's last two sunsets added a brand.


This is the second piece on Google's AI shelf. The map of the six doors is the setup. Grok and Claude Desktop are the comparison.

Firebase Studio is the clearest example, because Google has already admitted the problem in public and then demonstrated it again.

What "retired" means on this calendar

The sequence is short enough to memorize, which is part of why it stings.

Project IDX became Firebase Studio: a browser IDE, Gemini in the loop, full-stack apps, the Firebase name wrapped around a cloud workstation. Then, on March 19, 2026, Google announced the sunset. New workspace creation and signups stopped on June 22, 2026. The lights go out on March 22, 2027, and leftover workspace data is deleted. Firestore, Auth, and App Hosting stay. The IDE is what leaves.

The recommended landings are Google AI Studio and Antigravity. Antigravity even ships a Firebase Studio migration doc, because "download your code and open the new IDE" is now a product surface of its own.

That is a real retirement. It is also a twelve-month lobby. From June 2026 to March 2027, anyone who bookmarked Firebase Studio can still open old workspaces, while anyone new is told the future is two other products. Search does not render that nuance. It renders three official Google pages that all claim to be where you build.

Then the terminal did the same trick

On May 19, 2026, Google moved consumer Gemini CLI onto Antigravity CLI. The post is unusually direct. Workflows outgrew the 2025 terminal. The fix is one platform. Antigravity CLI, written in Go, shares its harness with Antigravity 2.0. Skills, hooks, subagents, and extensions come across, extensions under a new name, plugins.

The consumer cutoff was June 18. Pro, Ultra, and free individual accounts stop getting answers from Gemini CLI. Enterprise Gemini Code Assist, and anyone on a paid Gemini or Gemini Enterprise Agent Platform API key, keeps the old CLI.

So the retirement has a trap door. Individuals are on Antigravity CLI. Companies on the license Google actually sells to IT departments are still on Gemini CLI. Both are "Gemini in the terminal" in a conversation, and they are different binaries, different support promises, and different brand names. A team with one contractor on Ultra and one seat on Code Assist Enterprise now has two supported terminals for the same chat.

Google called this pouring energy into a single product. The single product is Antigravity, plus the product they promised enterprises they would not turn off, plus the studio that is still up for existing workspaces.

Managed agents are a third door wearing the new name

The part that makes the menu feel dishonest is the agent layer, because it refuses to sit in one box.

The Antigravity agent on the Gemini API is a managed agent: sandbox, tools, files, web, defaulting to Gemini 3.8 Flash on the current preview. You call it from the API. You can also prototype it inside AI Studio, where the Playground has an Agents switch and a pile of templates. The templates preconfigure that same Antigravity agent.

Count the brands in one task. You open AI Studio. You toggle Agents. The base agent is Antigravity. The model is Gemini. If the project started life in Firebase Studio, the migration guide may have already sent you toward the Antigravity IDE, whose terminal cousin is Antigravity CLI, unless your company is still on Gemini CLI.

That is eight nouns for "ask the model to change the repo." A focused tool hides the nouns. Google printed them on the navigation.

Retiring a name is the product decision

The engineering story inside these posts is reasonable. A cloud IDE preview, a terminal that started as a Gemini demo, and an agent harness do not all need to live forever as separate apps. Merging them is what a serious platform does.

The consumer story is the opposite of the blog headlines. Simplifying, in the posts, means a migration guide, a second CLI, a desktop version number, an SDK, and a sunset that runs until spring 2027. The old names are not redirected into silence. They are documented, dated, and left searchable. People do not experience that as focus. They experience it as a company that starts more AI tools than it is willing to finish in front of an audience.

Focus would look boring. One developer URL. One terminal command. A retired page that says, in a single line, where the work moved, and then gets out of the search results. Firebase the backend can keep its name. The IDE that borrowed it cannot linger for a year next to the IDE that replaced it and the playground that also hosts the agent.

The menu got longer because each correction shipped as a new product name instead of a rename of the last one. That is the clutter. The last piece puts Grok and Claude Desktop next to it, from the same user's chair.

ThinkReview keeps the choice at the model, not the doorway. Gemini is on the list in model selection. The product around it does not get a new brand every time the harness moves.