Google releases then pulls COSMO app

Google briefly put a new Android app called COSMO on the Play Store, then pulled it back down. That sounds minor, but the app description made the bigger point pretty clear — Google is still figuring out what an AI assistant should look like when it lives inside Android itself, not just inside the Gemini app. The gap has been obvious for a while. Gemini can answer questions well, but replacing the old Google Assistant means handling all the little phone tasks people expect without friction. COSMO looked like an early attempt to close that gap. (9to5google.com) ### What was COSMO, exactly? The Play Store listing called COSMO an “experimental AI assistant application for Android devices,” and the package name tied it to Google Research rather than a normal consumer app team. Even so, it was published through Google’s main Play Store account, which is why the listing got attention fast. The app was then removed, which strongly sugge(9to5google.com)ntended audience. (9to5google.com) ### Why did people notice it so quickly? Because COSMO did not look like a random prototype. It was a hefty 1.13 GB download, and the listing said it brought AI “directly onto your device.” That size matters. It points to a bundled local model rather than a thin client that just sends everything to Google’s servers. In other words, this was not just another front end for cloud Gemini. It looked like a serious on-device assistant experiment. (9to5google.com) ### What could it actually do? The most interesting part was the skill list. COSMO could suggest Keep lists, draft documents, create calendar events from conversations, set timers, look up photos, summarize recent conversations, explain jargon, provide context about people or events, and trigger a web search when needed. One item stood out even more — a “Browser Agent” that(9to5google.com) assemble a fuller answer when a question needed multiple sources. Basically, Google was testing an assistant that listens for intent and jumps into action before you manually open five different apps. (9to5google.com) ### Why is the on-device angle the real story? Because that is the hard part of modern phone AI. Cloud models are more capable, but they add latency, depend on connectivity, and raise privacy questions. Local models are faster and feel more native, but they are constrained by battery, memory, and heat. COSMO’s settings showed Google trying to split that difference. Users co(9to5google.com) model online and Nano offline. Even without full clarity on “PI,” the structure is obvious: Google is testing when to keep assistant work on the phone and when to hand it off to the cloud. (9to5google.com) ### How does this fit with Gemini? COSMO looks like a missing layer between Gemini-the-chatbot and Android-the-operating-system. Gemini already shows up across Google products, but a real phone assistant needs to watch for context, understand casual speech, and take actions across apps. COSMO’s feature list reads less like a standalone chatbot and more like an operating-sys(9to5google.com) around Gemini-era models. (androidpolice.com) ### Is this headed for Google I/O? Maybe, but that part is still inference. Google I/O 2026 is scheduled for May 19 and 20, which makes the timing hard to ignore. A leaked or premature Play Store listing a couple of weeks before I/O is exactly the kind of thing that can happen when launch prep gets messy. Still, Google has not announced COSMO publicly, and experimental apps do sometimes disappear without becoming products. (androidpolice.com) ### So what’s the bottom line? COSMO matters less as an app than as a signal. Google accidentally showed a version of the assistant it seems to want next — more proactive, more embedded in Android, and more willing to run directly on your phone. Whether the name survives almost doesn’t matter. The bigger takeaway is that Google is still building the real post-Assistant experience, and COSMO gave us a quick look at the blueprint. (9to5google.com)