TL;DR
- The Google app is working on “Robin,” a shared Gemini agent you can add to a group chat or email thread — one assistant that works on behalf of everyone in the conversation, not just you.
- Supporting code points to a human-in-the-loop design that pauses to ask for confirmation, plus a usage limit banner that hints the agent is metered — and possibly paid.
- We found the strings in Google app v17.34.24, pulled from a Pixel running the Android 17 QPR1 beta and diffed against the previous v17.33.33 build. It isn’t live yet, and like any work-in-progress code it could change or never ship.
Gemini inside the Google app has, until now, been a strictly private affair: you ask, it answers, and the conversation is yours alone. A teardown of the latest beta — Google app v17.34.24, which we pulled straight off a Pixel and diffed against the previous v17.33.33 build — points to something far more social, under an unannounced internal name: Robin.
The most striking find is a cluster of new strings describing a Gemini agent that lives inside a shared conversation. One headline reads assistant_robin_identity_agents_headline → “Help your group get more done,” and the subtitle spells out the pitch with unusual clarity: “Add a shared agent to your group chat or email thread and let it handle admin for everybody.”
That single line is the whole story. Rather than each person quietly querying their own assistant, Robin appears to be a single agent that sits in a group chat or an email thread and acts for the entire group. Surrounding strings reinforce the idea of an in-conversation surface — “Copy” and “More options” controls tied to a shared conversation, plus “Active” and “Default” labels that suggest more than one agent is available, with one set as the group’s default.
Human-in-the-loop, with usage limits
Two further strings hint at how Google plans to keep an autonomous agent in check. A banner titled assistant_robin_agent_actuation_banner_title reads “Gemini needs your help with this step” — the language of a human-in-the-loop model, where the agent pauses an action and waits for a person to confirm before proceeding. That’s a sensible guardrail for an assistant operating across a whole group.
A separate quota banner, assistant_agent_quota_low_banner_text, resolves to “You’re at [X]% of your current usage limit.” The presence of a usage limit at all strongly implies metered — and possibly paid — agent activity, in line with how Google has been positioning its more capable Gemini features.
The evidence
The new strings in Google app v17.34.24:
assistant_robin_identity_agents_headline = "Help your group get more done"
assistant_robin_identity_agents_subtitle = "Add a shared agent to your group chat
or email thread and let it handle
admin for everybody"
assistant_robin_agent_actuation_banner_title = "Gemini needs your help with this step"
assistant_agent_quota_low_banner_text = "You're at %1$d%% of your current usage limit"
assistant_robin_eval_active_label = "Active"
assistant_robin_eval_default_label = "Default"What’s not new here
The same build also includes assistant_chat_branch_conversation_ready → “Your branch is ready,” which lets you fork a thread into a new conversation. It’s tempting to fold that into the Robin story, but branching isn’t a fresh discovery — the concept already exists in adjacent Gemini surfaces, so we’re treating it as context rather than part of this leak. A separate cluster of obfuscated keys (assistant_pcdos_*) also appears, but their meaning isn’t clear from the strings alone; prefixes like that typically group unreleased config and aren’t user-facing.
For context, Google already ships personal Gemini agents — proactive briefings, inbox-watching features — but none of those act as a shared participant inside a single thread on behalf of all its members. That’s what makes Robin different.
Google hasn’t said a word about Robin, and none of this is live yet. But a shared, in-thread agent that can “handle admin for everybody” would be a meaningful step beyond today’s one-to-one Gemini — and a clear signal of where Google wants its assistant to go next. We’ll keep an eye on future betas and update if and when it surfaces.
