Google’s experimental CC family agent gets a separate Google Account and shared household permissions

• Product: Google Labs CC, family/group version announced September 17, 2026.
• Model/version: Google says “latest Gemini models,” but does not name an exact Gemini model version. Google
• Access: Early Labs experiment; web and mobile; U.S.; age 18+; personal Google Account; existing CC users get upgrade email, new users join waitlist. Google
• Group size: up to six members. Google
• Inputs/actions: selected emails, forwarded one-offs, photos, PDFs, Drive folders/files, Chat, Calendar; shared daily brief, Calendar/Tasks updates, meal planning, lists, pre-filled forms. Google

Documented architecture is sparse but notable: each CC has a verified Google Account, runs on an isolated cloud computer, and is powered by Google’s agentic harness “Antigravity” plus Gemini models. That suggests an implementation pattern for multi-user agents: separate principal, scoped permissions, shared memory segmentation, and tool execution through first-party APIs. Google reports integrations with Gmail, Chat, Docs, Calendar, Drive, Tasks and Maps API. No reproducible evals, model card, benchmark suite, red-team report, latency data, or failure-rate data are published in the reviewed sources. Google

• Vendor-reported: CC has its own verified Google Account and permission model, only responds to group members, and will not act/share outside the group without permission. Google
• Vendor-reported: auto-“cc” lets users select recurring senders; a weekly private list lets users approve new senders. Google
• Independent reporting: Ars, TechCrunch and Engadget/Yahoo corroborate the launch, six-member family framing, shared daily brief, and separate-account design. Ars Technica TechCrunch Yahoo/Engadget
• Commentary: the linked post/video frames CC as a move from private assistants to shared household operations. 00:00

CC extends Google’s December 2025 single-user productivity agent and May 2026 Daily Brief in Gemini. The market context is consumer agentic AI moving from chat into persistent task systems, with TechCrunch naming family-oriented tools such as Ollie and Fambot as adjacent efforts. For practitioners, the design pattern echoes enterprise service accounts: a non-human actor with scoped access, audit-relevant identity, and tool permissions. That is the real precedent, more than the meal-planning use case. Google TechCrunch

CC is an experiment, not a generally available product. Reported FAQ constraints include: no searching personal inboxes, no purchases, no credit-card entry, no legal/school waiver signing, and no individual member removal after acceptance. Bitcritiq also reports that deleting an email in Gmail does not remove it from CC memory; full clearance requires deleting the CC account. These are product-control claims, not independent safety evaluations. Independent performance, hallucination, access-control bypass, prompt-injection, and privacy-retention testing were not found in the reviewed sources. Bitcritiq Yahoo/Engadget

For Google-heavy households and SMB-like family operations, CC could reduce coordination costs by turning scattered inbox/calendar data into shared operational state. For builders, the design lesson is clear: multi-user agents need first-class identity, revocable/scoped data channels, shared/private memory boundaries, and explicit approval gates. For vendors, this raises the bar above “connect my inbox” assistants. For risk teams, adoption should wait for admin controls, audit logs, retention controls, export/delete guarantees, and independent testing—especially where household data includes children, health, school, location or payments.