Google has quietly set a hard deadline for one of Android’s longest-running features. Support documentation for Android Auto now states that “Google Assistant is still available for use until March 2026,” a line first flagged by Android Central and 9to5Google in late November 2025 and now confirmed as accurate breaking news heading into the cutoff window. The wording is a soft deadline rather than a single kill-switch date, but the intent is unmistakable: Gemini is taking over voice control in cars, and Google Assistant’s run as the default in-car assistant is ending.
For the millions of drivers who say “Hey Google” to send a text, start navigation, or skip a song while behind the wheel, the assistant answering back is about to change. This is not a minor UI refresh. It is the closing chapter of a decade-old product, and it lands alongside a much bigger retirement wave that TechRepublic reports will hit Android phones, tablets, Wear OS watches, and connected earbuds later in 2026.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What Google’s Android Auto support page actually says
The change surfaced first not in a press release but in a support document. Google’s Android Auto help page on talking to Gemini or Google Assistant was updated with language telling users that the classic assistant “is still available for use until March 2026,” after which Gemini takes over the voice experience in cars connected through phone projection. That specific phrasing appears across multiple outlets that reviewed the same page, including Android Central, 9to5Google, PCMag, and TechRadar, all of whom flagged the update within days of each other in late November 2025.
Google support material also states plainly that “Gemini is taking the place of Google Assistant on most mobile devices,” a line that appears on both the general Assistant retirement pages and the Android Auto-specific documentation. That is about as close to an official confirmation as Google typically offers for a phased product sunset. The company has not issued a dedicated press release naming a single hard cutoff date, which is why outlets like PCMag noted lingering ambiguity over whether the switch lands on a specific day in February or spreads across March 2026 as a rolling migration.
A separate Google Help Center community thread adds detail on mechanics: the Gemini rollout for Android Auto began server-side in December 2025, and Google’s own moderators indicated that “by the end of March 2026 at the latest, every user should have received Gemini in Android Auto.” That framing suggests March 2026 functions less as a single detonation date and more as the finish line for a staged rollout that has already been running for months.
Gemini replaces Assistant in Android Auto, but not everywhere
The distinction that matters most for drivers is between Android Auto and Android Automotive. Android Auto is the phone-projection system that mirrors your phone’s interface onto a car’s built-in screen. Android Automotive is the deeper, embedded operating system found in vehicles with “Google built-in,” running independently of a connected phone. According to TechRepublic’s reporting on the wider Assistant retirement, cars with Google built-in will keep Google Assistant running beyond the broader September 2026 mobile deadline, because that system sits on a different software track entirely.
That leaves Android Auto, the far more common setup since it works with essentially any phone-compatible vehicle on the road, as the segment losing Assistant first. Drivers who rely on Android Auto through a plugged-in or wirelessly connected phone are the ones seeing Gemini prompts arrive in their dashboards now, months ahead of the broader mobile phase-out.
Two different countdown clocks
It helps to separate the two retirement tracks Google is running in parallel, because conflating them is where a lot of the public confusion originates:
The first track is Android Auto specifically, where support pages point to March 2026 as the point after which Assistant is no longer available and Gemini becomes the only option. The second, larger track is the general Android Assistant retirement, where TechRepublic reports Google is starting “the final phase” on September 4, 2026, covering phones, tablets, Wear OS, and paired headphones. Android Auto’s March cutoff effectively acts as an early wave inside that larger migration, arriving roughly six months ahead of the rest of the ecosystem.
Why Google is retiring a decade-old assistant now
Google Assistant launched in 2016 as a Google Home and Pixel feature before expanding across Android, cars, TVs, and smart speakers. It became one of the most widely deployed voice interfaces on the planet, running on hundreds of millions of devices. Gemini, Google’s large language model family, has been positioned since 2023 as the successor technology, but the company held off on a full assistant-level replacement for years while Gemini’s conversational and reasoning capabilities matured.
The timeline reported by Chrome Unboxed and referenced in the wider retirement coverage suggests Google originally intended a faster switchover and then pushed it back to give the transition more runway, aiming for what internal planning reportedly called a more seamless handoff. That would explain why the Android Auto migration started quietly through server-side rollouts in December 2025 rather than a single flag-day switch. A staged rollout lets Google catch integration bugs, such as third-party app compatibility or in-car microphone handling, before the assistant becomes mandatory for every user.
The business logic is straightforward even without an official statement spelling it out: Google wants one assistant, not two, and it wants that assistant to be the one built on its most current AI model family so improvements ship to a single product rather than being split across legacy and modern codebases. Running Assistant and Gemini in parallel indefinitely doubles engineering and support overhead for a company that has spent much of 2025 and 2026 consolidating its AI efforts under the Gemini brand across search, Workspace, Android, and now cars.
How the two assistants compare inside a car
Comparing Assistant and Gemini inside Android Auto is less about raw AI capability and more about what changes in the specific context of driving: hands-free reliability, latency, and how well each assistant handles the narrow set of tasks people actually want while moving.
| Capability | Google Assistant (legacy) | Gemini in Android Auto |
|---|---|---|
| Underlying model | Rule-based + earlier NLU stack | Gemini large language model family |
| Availability in Android Auto | Until March 2026 per Google support pages | Rolling out server-side since December 2025 |
| Status in Android Automotive (built-in) | Continues beyond the mobile deadline | Being introduced in parallel, per Google |
| Opt-out available | Temporary rollback possible in some cases | Becomes the only option once migrated |
| Positioning per Google support text | Being phased out | “Taking the place of Google Assistant on most mobile devices” |
| Standalone app fate | Expected removal from Play Store post-transition | Not applicable â built into Android/Gemini app |
Google has not published a detailed public benchmark comparing response latency or task accuracy between the two systems specifically inside Android Auto, so any claims about Gemini being measurably “faster” or “smarter” behind the wheel should be treated as unverified until Google or a third-party reviewer publishes hands-on data. What is documented is the rollout mechanism and the account-level switch, not a side-by-side performance study.
The retirement timeline, mapped out
Because Google is running several overlapping deprecation clocks across its device categories, a simple timeline is the clearest way to track what happens when.
| Date | Milestone | Source |
|---|---|---|
| December 2025 | Gemini rollout begins server-side inside Android Auto | Google Help Center thread |
| Late November 2025 | Updated support-page wording spotted by press (“until March 2026”) | Android Central, 9to5Google, PCMag, TechRadar |
| March 2026 | Target date for Google Assistant to stop working in Android Auto | Google Android Auto support documentation |
| End of March 2026 | Google’s stated goal for every Android Auto user to have received Gemini | Google Help Center thread |
| September 4, 2026 | Final phase of the broader Google Assistant retirement on phones, tablets, Wear OS, and earbuds begins | TechRepublic |
| Beyond September 2026 | Google Assistant continues only in Android Automotive (built-in) vehicles | TechRepublic |
Notice the gap between the Android Auto cutoff and the broader mobile retirement: roughly six months separate the two. That gap is worth paying attention to, because it means a driver could lose Assistant in the car well before losing it on their phone’s home screen, creating a stretch where the same person uses Gemini in the car and Assistant everywhere else on the same device.
What drivers are actually saying
Reaction in Google’s own support forums has skewed toward frustration rather than enthusiasm, based on threads reviewed in this reporting. One widely referenced Google community thread was titled “Need ability to disable Gemini in Android Auto,” and a moderator response reportedly summed up the reality bluntly: any rollback option is “not easily, and not for long” available, with Google actively disabling legacy servers on a rolling basis. That is a familiar pattern for major platform migrations: the company offers a brief grace period for holdouts, then removes the fallback once adoption data shows most users have already moved over.
The friction point for many drivers is not the AI model underneath but muscle memory. Voice commands during driving are one of the few interactions people expect to work identically every single time, without needing to relearn phrasing or wait through a slower response. Any assistant swap in a moving vehicle carries higher stakes than the same swap on a phone sitting on a desk, which is part of why Google appears to be moving Android Auto through a longer, staged rollout rather than an instant switch.
Market and competitive context: Amazon, Apple, and the voice-assistant race
Google is not alone in overhauling its car-connected voice assistant during this period. Apple has been layering generative AI features into Siri and CarPlay, and Amazon has pushed its own Alexa+ overhaul into more vehicles and smart-home hardware through 2025 and 2026. The difference with Google’s move is scale and abruptness: Android Auto ships on the overwhelming majority of Android-compatible vehicles sold globally, meaning a single support-page update effectively resets the default in-car assistant experience for a very large share of drivers at once.
That scale is also the commercial logic behind the move. Every car dashboard running Gemini instead of legacy Assistant becomes a new, high-frequency data point for Google’s broader Gemini strategy, and a proving ground for how well an LLM-based assistant performs under real-world constraints like road noise, spotty connectivity in tunnels or rural areas, and split-second command execution. If Gemini performs reliably in that environment, it strengthens Google’s pitch to automakers building next-generation Android Automotive systems, where Google is competing for embedded-software contracts against in-house systems from automakers and against Apple’s expanding CarPlay ambitions.
Historical context: assistant transitions rarely go smoothly
This is not the first time a major platform has forced users off a long-standing voice assistant. Microsoft wound down Cortana as a consumer assistant years ago, migrating functionality into other products with limited fanfare and plenty of user complaints about lost features. Amazon has repeatedly reworked Alexa’s backend without always preserving every legacy skill or routine, frustrating long-time smart-home users who built automations around specific quirks of the old system.
Google itself has a track record here too: Google Assistant absorbed and eventually replaced Google Now, and various Nest and Home product lines have gone through their own assistant consolidations over the years. The pattern that tends to repeat is a quiet support-page update first, media coverage second, official acknowledgment sometimes lagging behind both, and then a rolling migration that takes months rather than a single cutover day. The current Android Auto situation follows that exact sequence almost beat for beat.
What happens to devices that can’t run Gemini
Part of the broader 2026 Android changes documented by nokiapoweruser’s roundup of Google’s Android feature phase-outs concerns older hardware. According to that coverage, phones running Android 8.0 or below will stop receiving Android Auto updates altogether, separate from the Assistant-to-Gemini switch but happening on a similar timeline. That means some drivers may lose full Android Auto functionality for reasons unrelated to the assistant swap, simply because their phone’s OS version has aged out of support.
For most current-generation phones, running a reasonably recent Android release, the transition should be transparent: Gemini arrives through a server-side update with no user action required, and the interface inside Android Auto continues to look largely the same, aside from branding and, presumably, differences in how commands get interpreted. Google has not published a minimum RAM or chipset requirement specific to running Gemini inside Android Auto, so drivers with genuinely old or low-spec phones should watch their own device’s update history rather than assume compatibility.
What this means for third-party app integrations
Android Auto’s usefulness depends heavily on how well voice commands route into third-party apps: messaging platforms, navigation alternatives, and music or podcast services that plug into the car interface. Any assistant swap carries risk for that integration layer, since voice intents that used to route cleanly to a specific app through Assistant’s older command-parsing system need to be re-validated against Gemini’s newer natural-language handling.
Google has not published a detailed compatibility list confirming which third-party Android Auto apps are fully validated against Gemini as of this writing, which is a legitimate open question for developers and users relying on non-Google apps in the car. Until Google or app developers confirm specifics, drivers who depend heavily on a particular third-party integration should treat the transition period as a time to double-check that familiar voice commands still trigger the expected app behavior.
Predictions: where this goes next
Based on the documented rollout pattern and Google’s broader Gemini consolidation strategy, several outcomes look likely over the next 12 months.
First, expect the March 2026 Android Auto deadline to slip by weeks rather than months if it slips at all, following the same pattern Google already showed by delaying the original mobile Assistant retirement into 2026 to smooth the rollout, as reported by Chrome Unboxed’s coverage of the broader migration.
Second, the standalone Google Assistant app is likely to disappear from the Play Store once the September 2026 mobile phase completes, consistent with reporting on Google’s plans for the wider retirement.
Third, Android Automotive (the built-in, non-phone-projection system) will likely keep Assistant running well into 2027 for existing vehicles already on the road, even as new vehicle software builds increasingly ship with Gemini as the default from day one.
Fourth, expect Google to publish more detailed migration and compatibility documentation as the March 2026 deadline approaches and support ticket volume rises, since the current support-page language leaves real ambiguity around exact dates that a company managing a mass migration typically needs to resolve publicly.
Fifth, competitive pressure from Apple’s CarPlay AI features and Amazon’s Alexa+ push into vehicles will likely accelerate rather than slow Google’s Gemini rollout in cars, since ceding voice-assistant mindshare in the automotive space carries strategic weight beyond the car itself, feeding into broader assistant market share on phones and smart-home devices.
What drivers should do before the cutoff
There is no action required to receive Gemini in Android Auto since the rollout is server-side and automatic, according to Google’s own support documentation. Drivers who want to check their current status can open the Android Auto settings menu on their connected phone and look for assistant-related settings, where Gemini will either already be active or listed as pending. Anyone who prefers to test the new assistant ahead of the mandatory switch can typically opt in early through the Google app’s assistant settings, though Google has not guaranteed early opt-in availability on every device.
For drivers concerned about losing specific routines or voice shortcuts built around legacy Assistant behavior, the practical step is to test common commands, sending a text, starting navigation, controlling music, checking the weather, as soon as Gemini activates rather than waiting until the old system is fully gone. That gives time to report issues to Google or find workarounds before Assistant stops being available as a fallback.
Frequently Asked Questions
When exactly does Google Assistant stop working in Android Auto?
Google’s Android Auto support documentation states Assistant “is still available for use until March 2026,” which functions as a rolling cutoff rather than one single date, according to reporting from Android Central and 9to5Google.
What replaces Google Assistant in Android Auto?
Gemini. Google’s support text says “Gemini is taking the place of Google Assistant on most mobile devices,” and the Android Auto rollout of Gemini began server-side in December 2025.
Will Google Assistant still work in my car after March 2026?
It depends on the type of system. Android Auto (phone-projection) is losing Assistant on the March 2026 timeline. Android Automotive, the built-in system in some newer vehicles, keeps Google Assistant running beyond that date, per TechRepublic’s reporting on the wider retirement.
Can I opt out of Gemini and keep using Google Assistant in Android Auto?
Only temporarily in some cases. A Google support thread indicates that rollback options are limited and short-lived, since Google is progressively disabling the legacy Assistant servers that Android Auto relies on.
Is this the same as the broader Google Assistant shutdown on Android phones?
It’s related but on a separate, earlier timeline. TechRepublic reports the final phase of the broader Assistant retirement across Android phones, tablets, Wear OS, and connected earbuds begins September 4, 2026, roughly six months after the Android Auto-specific cutoff.
Do I need to update my phone to get Gemini in Android Auto?
Google has not published a specific minimum Android version requirement for Gemini in Android Auto. Separately, phones running Android 8.0 or older are losing general Android Auto update support, according to nokiapoweruser’s coverage of Google’s 2026 Android changes, which is a different issue from the Assistant-to-Gemini switch.
Will the standalone Google Assistant app disappear from the Play Store?
Reporting on Google’s broader retirement plan suggests the standalone Assistant app is expected to be removed from the Play Store once the wider mobile transition completes, though Google has not confirmed an exact removal date.
Where can I check official details on this change?
Google’s own Android Auto support pages are the primary source, alongside the Google Gemini product blog for broader assistant strategy updates.
