Google Rebuilds CC to Manage Schedules for Entire Households

Google Labs is reworking CC, its experimental personal AI agent, for household scheduling and coordination. Up to five other people can join, bringing the household total to six. The agent receives its own Google account and coordinates opted-in email, calendars, tasks, documents, and chat while preserving separate permissions for each member.

Google introduced CC on December 16, 2025, as a personal productivity agent that connected Gmail, Google Calendar, Google Drive, and the web. It delivered a “Your Day Ahead” briefing by email each morning. Early access covered consumer-account users aged 18 and older in the United States and Canada, starting with Google AI Ultra and other paid subscribers. In May 2026, Google brought the underlying experience to the Gemini app as Daily Brief. The latest version extends that model from one user to a household.

Shared access gets its own identity

Giving CC a Google account makes the agent a distinct identity within Google’s permissions system. Each household member chooses which information to share, including selected school emails, appointment confirmations, and calendars. Google can therefore manage the agent’s access independently of any member’s login.

One parent might share messages from a school, another could provide pediatrician confirmations, and a teenager could connect a calendar without opening the rest of their Gmail. Google says CC runs on its Antigravity agent runtime and the latest Gemini models using isolated cloud computers. Under a member’s direction, it can pre-fill PDF forms, check current drive times through the Google Maps API, and create shared files in Google Docs and Sheets.

A day routed through CC

Household members interact with CC through a shared morning email and a Google Chat space. The agent gathers approved information, turns it into a daily plan, and handles assigned logistical work.

• Creates a shared “Your Day Ahead” brief from opted-in inboxes and calendars
• Writes schedules and to-dos to a shared Google Calendar and Google Tasks list
• Accepts requests for errands, meal plans, and shopping lists through Google Chat
• Pre-fills permission slips, registrations, and other paperwork under user direction
• Separates household-wide context from individual preferences in memory

Scoped memory allows CC to apply facts only where they belong. It can remember that a household eats vegetarian meals while tracking that one member is lactose intolerant. A shared agent must also account for overlapping schedules, conflicting requests, different communication habits, and individual privacy settings.

Google widens the circle

CC gives Google a way to connect assistant features that have appeared across Labs and Gemini. Google says it brought CC to the Gemini app as Daily Brief; the household release applies the same agent model to several users, shared resources, and separate permission boundaries.

The design also ties Gmail, Calendar, Tasks, Chat, Docs, and Maps into a recurring household workflow. As CC accumulates school schedules, appointments, preferences, and task history, moving that workflow to another provider requires more setup and data migration. That raises switching costs across Google’s consumer services.

Who gets the upgrade

The household version remains an early Google Labs experiment. Its rollout varies by account, location, and signup date.

A shared-agent blueprint

CC demonstrates a multi-user agent architecture in which several people grant scoped access to one service while retaining separate preferences and private data. Most consumer agents assume one owner, so the household model introduces design requirements that also apply to roommates, small teams, and community groups.

1. Independent identity: The agent has an addressable Google account with permissions that can be managed separately from household members.
2. Source-level consent: Members can limit access to selected email sources and calendars.
3. Partitioned memory: Shared facts and individual preferences occupy different scopes, reducing the risk that one person’s context affects another’s request.
4. Shared outputs: The agent writes plans and tasks into collaborative Google services instead of keeping results inside a private chat session.

Google has yet to explain several implementation details developers will want to track, including how revoked access affects stored memories, how CC resolves conflicting instructions, how long shared context is retained, and whether activity logs identify which member supplied each fact or request.

Household adoption will depend on whether members trust the permission controls, memory boundaries, and handling of sensitive schedules and messages. The same account, consent, and memory architecture could support other groups that currently coordinate through shared spreadsheets, calendars, and group chats.