Google Labs launches CC, an email-native productivity agent built on Gemini

What CC actually does

CC connects a user's Gmail, Google Calendar, Google Drive and the wider web, then emails a "Your Day Ahead" briefing every morning. The briefing synthesizes schedule, key tasks and updates into a single summary — the source names concrete examples like paying a bill or preparing for an appointment.

Beyond summarizing, CC prepares email drafts and calendar links so a user can act without leaving the flow. And it accepts steering: you reply or email it directly with custom requests, teach it facts about yourself, or ask it to remember ideas and todos.

It is launching in early access to Google consumer account users aged 18+ in the U.S. and Canada, starting with Google AI Ultra and paid subscribers, behind a waitlist. Google labels it an early Labs experiment.

The inbox is the interface

The most notable design decision here isn't the model — it's that CC has no screen of its own. Its output arrives as an email, and its input channel is a reply to that email. Google is treating the inbox as the entire frontend surface.

That has real advantages. There's nothing to install, nothing to learn, and the interaction model is one every user already understands: read a message, write a reply. Threading gives the agent a durable conversation history for free, and drafts and calendar links slot into affordances Gmail already renders.

It also imposes constraints. Email is asynchronous and unstructured — a reply is free-form text, not a typed command, so CC has to parse intent from prose like "remember this todo" or "teach it things about yourself." There's no undo button, no confirmation dialog, and no obvious place to show state. The frontend a team would normally build to disambiguate a request doesn't exist; the model has to absorb that job.

What steering-by-reply demands under the hood

The source says users can teach CC things about themselves and ask it to remember ideas and todos. That implies persistent per-user memory that accumulates across messages, plus a resolution layer that decides when a reply is a new task, a correction, a fact to store, or a request to draft something.

Pairing that with read access to Gmail, Calendar, Drive and the open web means CC is fusing several private data sources into one outbound summary each morning. The "Your Day Ahead" briefing is essentially a scheduled synthesis job, distinct from the interactive reply loop — two different execution paths sharing the same memory store.

The implication: an agent that meets users where their work already lives

CC's specific bet is that a productivity agent doesn't need its own destination. By making email both the delivery mechanism and the control channel, Google reduces the adoption cost to zero installs and leans on a format users check daily anyway.

For teams building agents, the lesson from this launch is narrow and concrete: choosing an existing communication surface as the interface trades polished UI control for immediate reach, and shifts the burden of intent parsing and state management from the frontend onto the model and its memory. CC is Google testing that trade-off in early access — a limited, waitlisted experiment rather than a shipped product, which is the honest framing for anyone evaluating the same approach.