Google CC
Google (Google Labs) · labs.google/cc
CC is a hosted, proprietary Google Labs agent that runs from a Google-operated account on Google's Antigravity harness and Gemini models. Members control what they share with it and can delete their accounts or the group. The agent cannot be exported, inspected, re-hosted or moved to another model, and its memory cannot be viewed or edited item by item.
- Members choose which senders, emails, files and calendars CC can see, and can revoke access
- CC acts only for group members and needs confirmation before sharing outside the group
- A separate agent account keeps its permissions apart from members' accounts
- Per the disclaimer, CC data is not used to train Google's foundational models
- Account and group deletion are available in settings
- No export; runs only on Google's proprietary hosted harness
- Gemini only, with no choice of model
- Memory cannot be viewed or edited item by item
- No owner-visible action record, and no way for recipients to verify its messages
- Experimental, waitlisted service that Google can change or end
All 34 findings
Google Labs early-access experiment as expanded on September 17, 2026 (a group agent with its own Google Account, up to six US adult members, waitlist), with reference to the December 16, 2025 individual launch. Assessed from public documentation only.
Portable · Can you leave, and take the whole agent with you?
0%- P1Round-trip portability
Incomplete and not restorable: no export of the CC agent's memory, configuration or instructions is documented and there is no import; the FAQ offers only deletion.
Fail - P2Complete export
CC's memory, instructions and executable logic stay in Google's hosted service and Google-operated account; no export of them is offered.
Fail - P3Independent execution
CC runs on an isolated Google cloud computer using Google's Antigravity agent harness and Gemini models. It is hosted-only, with no runnable export.
Fail - P4Identity continuity
CC's identity is a Google Account operated by Google, and nothing lets others verify it is the same agent apart from Google.
Fail - P5No kill switch
CC is a waitlisted Google Labs experiment that Google can change or end. No exported agent exists outside Google's control.
Fail - P6Capability independence
Tools, triggers (daily brief, Auto CC), messaging and memory are provided by Google's hosted harness and Gemini models, and none of them survive a move to another model or runtime.
Fail
Transparent · Can you see everything the agent is, with ordinary tools?
8%- T1Open storage format
CC's memory and state are stored in Google's proprietary backend in an undocumented format. Only its outputs in Gmail, Calendar, Tasks and Drive can be accessed, through Google services.
Fail - T2No hidden instructions
The system instructions that Google's agent harness places in the Gemini context are neither published nor viewable by members.
Fail - T3No shadow memory
The FAQ states that CC keeps its own memory, which is not removed when an email is deleted from Gmail, and no memory viewer is documented. Data is also processed under the general Google Privacy Policy.
Fail - T4Complete action history
CC's outputs appear as emails, Chat messages, calendar entries, tasks and Drive files in shared spaces, but no complete history of its actions and tool calls is available to members.
Partial - T5Readable logic
CC's logic is Google's proprietary harness code. Members cannot see its skills, workflows or code.
Fail - T6No third-party influence channel
Google does not document advertising or sponsored content in CC. It has also not stated whether CC data is used to personalize ads.
Unverified
Auditable · Can you reconstruct exactly what the agent did?
0%- A1No unrecorded actions
Google does not document whether every consequential CC action is durably recorded, or whether an action that cannot be recorded is blocked.
Unverified - A2Tamper evidence
Members are given no action record, so they cannot detect edits to or deletions from one.
Fail - A3Separation from the audited
Google does not document whether CC can alter or delete records of its own actions.
Unverified - A4Readable with ordinary tools
No audit trail is published to members. Only CC's outputs in Google services are visible.
Unverified - A5Corroborated interactions
No record of CC's exchanges is available to members that could be matched against the other side's records, beyond the messages themselves in shared spaces.
Fail
Verifiable · Can you prove the agent runs what it claims?
0%- V1Open, reproducible runtime
CC, its deployment of the Antigravity harness and the Gemini models are proprietary. None is published under an OSI-approved license.
Fail - V2Active config is inspectable config
CC's active configuration (system instructions, model version and harness settings) is held server-side and cannot be inspected by members.
Fail - V3Attributable messages
CC sends messages from its own Google-operated account; recipients can see that account but cannot verify the message was sent under members' authority, and this would not survive a move away from Google.
Fail - V4Independently checkable record
No action record or verification procedure is published for CC, so nothing can be checked with open tools.
Fail - V5Comparable state
CC's state is held server-side and its memory cannot be viewed, so members cannot verify whether it changed between two points in time.
Fail
Modifiable · Can you change anything, without asking?
17%- M1Instructions
Members can steer CC with replies, emails and feedback, which it remembers as preferences. They cannot read or rewrite its underlying instructions.
Partial - M2Memory
No memory viewer or per-item editing is documented. The FAQ says deleting a Gmail message does not remove it from CC's memory and that fully clearing data requires deleting the account; removing a sender deletes only that sender's emails from CC's inbox.
Fail - M3Logic
Members cannot change CC's skills, workflows or code.
Fail - M4Tools and permissions
Each member chooses which senders, categories, emails, files, folders and calendars to share, and can revoke them in Sharing Preferences. Members cannot add tools that Google does not offer.
Partial - M5Model choice
CC runs only on Google's Gemini models, with no choice of model.
Fail - M6No gatekeeping
Access requires a Google waitlist or invitation, and at launch CC was limited to Google AI Ultra and paid subscribers. No changes are possible beyond the settings Google provides.
Fail
Controllable · Is your word final?
42%- C1Communication boundaries
Google says CC responds only to group members and shares outside the group only with permission, but members cannot set their own contact rules, and whether enforcement sits outside the model is not documented.
Partial - C2Approval gates
CC needs member confirmation before sharing outside the group, and it cannot add or remove members. Members cannot choose which other actions require approval.
Partial - C3Immediate halt
Members can revoke sharing or delete the group, which removes the agent. No pause or immediate-stop control is documented.
Partial - C4Data sovereignty
The CC disclaimer says CC data is not used to train Google's foundational generative AI models. All content is processed on Google servers under the Google Privacy Policy, which cannot be verified by network inspection.
Partial - C5Credential custody
CC acts through its own Google-operated account with access held by Google. Members can revoke what they share, but they cannot hold, inspect or move the credentials.
Fail - C6Full deletion
In settings, 'Delete Account' permanently deletes a member's CC account and connected information, and 'Delete Group' deletes the agent and its shared spaces. Past CC emails stay in members' inboxes, and Google's general retention and deletion windows apply.
Partial
Vendors and the public can dispute any finding with evidence. Disputes and their resolutions are published.