Google’s COSMO leak looks less like a surprise product launch and more like a brief, accidental glimpse of Google’s next Android AI-assistant experiments. Multiple reports say a Play Store listing for COSMO appeared, described as an “experimental AI assistant application for Android devices,” and was then removed shortly afterward.[6][
1]
What happened to Google COSMO?
Reports say COSMO appeared on Google Play around May 1, 2026, shortly before Google I/O 2026, and was pulled within hours.[3][
6] 9to5Google reported that the app looked like a premature or accidental release and said it was “not meant for consumers.”[
6]
The listing was reportedly tied to the package name com.google.research.air.cosmo, which points toward Google Research, although 9to5Google noted it appeared under Google’s main Play Store account.[6] Another report said the app was about 1.13 GB, a size that stood out and suggested more than a lightweight chatbot wrapper, though the file size alone does not confirm exactly what was inside.[
2]
What COSMO appears to be
The available reporting describes COSMO as an experimental Android AI assistant or agent, not a finished app. Moneycontrol reported that the app included on-device AI for scheduling, automation, and contextual assistance.[1] Droid Life described it as an AI agent installed directly on the device, with Gemini Nano inside and possible offline operation.[
4]
That combination matters because it suggests COSMO may have been testing AI that can work closer to the phone’s operating context rather than functioning only as a cloud chatbot. Some coverage framed COSMO as part of a hybrid approach, combining on-device AI with heavier remote processing when needed.[2]
Reported capabilities, with caveats
The most consistent reported details are:
- On-device AI: Multiple reports describe COSMO as using Gemini Nano, Google’s smaller on-device AI model family, for local assistant features.[
1][
4]
- Automation and task help: Reports mention scheduling, automation tools, and contextual assistance, suggesting the app was built to help act on device-level tasks rather than only answer questions.[
1]
- Offline or local operation: Droid Life reported that COSMO included a Gemini Nano model that could run offline, although this remains based on reporting around the pulled listing rather than a public Google announcement.[
4]
- Hybrid AI architecture: One analysis described COSMO as revealing a hybrid architecture for next-generation assistants, but that interpretation should be treated as analysis of the leak, not confirmed product documentation.[
2]
The important caveat: none of this makes COSMO a confirmed upcoming consumer app. The most reliable reports characterize it as an experimental or pre-release listing that went live too early.[6][
4]
Why did Google pull COSMO?
The honest answer is that the available reports do not provide an official Google explanation. Coverage generally converges on the same likely scenario: an internal or experimental app listing was published prematurely, then removed once noticed.[1][
6]
The timing is why the leak attracted attention. COSMO appeared shortly before Google I/O 2026, and several outlets framed it as a possible early look at Google’s Android AI-agent direction ahead of the event.[6][
4]
How much should you trust the bigger claims?
Treat the core facts as higher confidence: COSMO was listed on Google Play, it was described as an experimental Android AI assistant, it appeared tied to com.google.research.air.cosmo, and it was removed.[6]
Treat more expansive claims — especially detailed feature lists from videos or secondary summaries — as lower confidence unless they are backed by the Play Store listing, screenshots, or APK analysis. The strongest available reporting supports the idea of a Google Research Android AI-assistant experiment with Gemini Nano and automation features, but not a finalized public product.[1][
4][
6]
Bottom line
COSMO appears to be a leaked or accidentally published Google Android AI-assistant experiment, likely connected to Gemini Nano and on-device automation. The removal is not especially mysterious on the evidence available: the strongest explanation is that a pre-release or internal test surfaced too early, and Google pulled it before any official announcement.[6][
1]






