Google's CC agent asks each of six household members separately what it may read

Say one member forwards the school thread and it has three unrelated things in it. This design turns on where those details land. Google said what the agent picks up goes into a shared household memory or a private one, depending on whether the item applies to everyone or to a single person ^[8]. Ars Technica reported that CC sees a member's email only when it has been explicitly shared ^[17].

In any shared agent, ask who granted the access and who can read what comes out. One grant with one reader gives you an ordinary personal assistant. Here, every member grants and every member reads. Private memory covers the six-grant, one-reader case ^[8]. That leaves one member granting while all six read, and Google's answer there is the classification into shared or private ^[8].

Tom Shane, senior product manager at Google Labs, wrote in the post announcing the change that "one of our top user requests was for CC to do more to help run a busy home" ^[9]. He said the coordination gets harder when the information is spread across separate accounts ^[10]. Google Labs said the agent's own account also gives it a clearer place to hold what each person has agreed to share ^[4]. An agent holding its own account can be granted access and cut off one member at a time, and an agent that signs in as somebody inherits whatever that person can reach.

Each CC runs on its own isolated cloud computer, built on Antigravity, Google's agentic harness for developers, and on the company's latest Gemini models ^[11]. The isolation is per household, not per person, so six people's pooled material sits inside one boundary.

CC started in December 2025 as a single-user product that emailed a briefing built from Gmail, Calendar and Drive, and moved into the Gemini app in May under the name Daily Brief ^[15][16]. The household version was announced on September 17, roughly nine months after the single-user one ^[19][18]. Existing users get an email about upgrading in the coming days, and everyone else joins a waitlist ^[14]. Google did not disclose a price ^[22].

The test I would apply before switching on a team agent is three columns for every source it reads: who granted it, who can read the output, and what ends the grant. CC answers the first two per member ^[2][8]. The third runs through a weekly list of new senders, one queue per member, which is six queues feeding one shared brief ^[20]. I would judge the model by how many senders a member still reviews in month three.