Google gives CC its own account to run a six-person household
Google Labs stopped treating its CC agent as a personal assistant and gave it a seat at the family table — with its own Google account and its own permissions model.
Google Labs is testing a new version of CC that runs a household rather than an individual, and the mechanism is the story: the agent gets its own Google account, a distinct identity, and a permission set that up to six family members negotiate with it. Google says the pivot came from user requests — people wanted help with school schedules, sports practices, bills and meal planning, not with their own work queue. So CC now reads what each member chooses to hand it: emails from the school, the swim center, the vet, and any sender a member whitelists permanently, such as a travel company, club or sports team. Everything it collects lands in a shared "Your Day Ahead" brief delivered to the inbox, with dates and to-dos pushed into Calendar and a shared Tasks list. CC suggests new senders to add on a weekly basis.
The agent is not read-only. With permission, CC fills out forms, including activity registration paperwork and PDFs, builds school supply lists, plans weekly meals, calculates drive times between activities, and creates shared Docs and Sheets. When something is missing — a form field, a date, a name — it asks, then writes the answer into a group memory so the next request goes faster. It runs on its own isolated cloud computer, powered by Gemini and Google's Antigravity agentic harness, which is the same harness the company has been pushing to its engineers. Google says the experiment is open to US users with a personal Gmail account, ages 18 and up, by waitlist.
That age floor is the flaw worth naming. The people whose inboxes hold the family logistics — tweens and teens with school-issued Google accounts — are locked out of the agent that exists to sort them, unless they misstate their age on a personal account. Google has built a household agent whose most valuable data source, the student inbox, sits behind an eligibility gate on exactly the users who own it. It also arrives into a crowded field: Ollie is pitching privacy as the differentiator for assistants, and Fambot already sells itself as a chief of staff for families. Google's advantage is not the idea; it is that CC can sit inside Gmail, Calendar and Tasks natively.
The permission model deserves more scrutiny than it will probably get. An agent with its own Google account that ingests family email is a new kind of data surface — shared, semi-autonomous, and authorized by whichever member clicked share. Google's framing is that CC "only sees what each member chooses to share," which puts the burden of access control on a parent who is already behind. Watch whether the waitlist expands past six members and whether Google publishes what happens to the group memory when a member leaves the household.
Would you hand a family agent your inbox if it saved you the school-form drudgery — or is the permission surface too wide to trust? Tell us in the comments.
