Google Assistant is going away. Starting September 4, 2026, Google will begin removing Assistant access from Android phones, tablets, Wear OS watches and phone-projected Android Auto, and once a device is switched over there is no way back. Gemini becomes the only assistant experience on Android — not a narrow, intent-matching tool but a general-purpose LLM.

What’s actually changing, and when

Google emailed existing Assistant users directly with the news, first reported by 9to5Google and confirmed by outlets that reviewed the same email:

  • The cutoff is September 4, 2026. Google will “begin removing access to Google Assistant starting on September 4,” and the rollout “may take a few weeks to reach everyone,” per the email text quoted by 9to5Google and Tom’s Guide.
  • It’s one-way. “Once availability is removed, you will no longer be able to use or switch back to Google Assistant on your phone, tablet or paired devices” — there’s no opt-out or rollback once a device converts.
  • Scope: Android phones and tablets, Wear OS watches, paired headphones and earbuds, and Android Auto when it’s phone-projected. Cars with Google built-in keep Assistant working past September 4. Google TV and Google Home devices aren’t part of this announcement, though 9to5Google notes Google has said Gemini is “coming” to both.
  • The trigger phrase survives the switch. “Hey Google” still works — it now wakes Gemini instead — and old Assistant voice commands are expected to keep functioning, per Tom’s Guide.
  • This date has already slipped once. The cutover “was originally set for the end of 2025 but was later extended to 2026,” per 9to5Google and TechRadar — worth keeping in mind, though a dated email to existing users is a firmer signal than the prior general roadmap statements were.

Why this is more than a UI refresh

The mechanism matters more than the branding. Assistant is a fixed-intent system: it matches a spoken phrase to a predefined action. Gemini is an LLM — the same category of system that reads and reasons over a page rather than pattern-matching a command. Google swapping the default voice/action layer on the majority of its Android install base from one to the other is, mechanically, the same shift this site already tracks on the search side: AI Overviews and AI Mode reasoning over page content instead of a ranked list of links. Now it’s happening on the assistant surface too, and it’s opt-out only in the sense that a user can delay installing Gemini — not in the sense that Assistant survives.

What to check before September 4

None of the three reports above mention shopping or commerce specifically — this is a platform migration announcement, not a feature launch — so the practical step for a merchant is narrower than “prepare for AI shopping.” It’s this: if any part of your customer experience depends on Google Assistant today — a “Hey Google, what are [store]’s hours,” a smart-speaker skill, a voice query that pulls your business info via Google — that flow now runs through an LLM instead of a fixed intent, with no guarantee Google preserved identical behavior in the swap, and no way to roll a converted device back to verify the difference. Test it once your own devices convert, rather than assuming continuity.

Sources

Whether it’s a search box, a chat window or now the default voice assistant on most Android phones, the pattern is the same: an LLM stands between your store and the customer, and it can only act on what it can actually read.