Google announced its Gemini agent on October 8. The agent gets its own Workspace account. It includes an email address, a calendar, Drive storage and a directory listing. The address takes the form agent-name@agents.company.com. The agent acts under its own identity. Every action it takes logs to that identity.
The estimating tool sends bid reminders from a shared Gmail address. The dog-training platform routes booking confirmations through a transactional email service. The construction ERP notifies subs when drawings change. Each email shows a from address. That address belongs to a system account I control. If an agent sends the email, the from address still points back to my domain. The recipient has no way to tell whether a human or an agent composed the message. The log shows the send and the timestamp.
The agent sits in the directory
Google provisions coworker agents the way it provisions employees. The agent gets a Workspace account. It appears in the directory. Colleagues can tag it in chat, email it directly or add it to a group. A coworker agent acts under its own identity rather than yours. It sees only what you share with it. The scoping is explicit. The identity is persistent.
Atelier routes inference requests to seven model providers. The flight planner calls a weather API. The permit app queries a zoning service. Each call runs under a service account or an API key. The key belongs to me. The log attributes every call to my account. I delegate a task to a model. The model makes 50 API calls to finish the work. All 50 calls bill to my account. The log shows my key. The distinction matters when someone asks who authorized the spend.
The log follows the agent
Google says the agent keeps four kinds of memory. Session memory persists across days. The agent works on a task, stops and resumes later. Every action the agent takes logs to its own identity. When the agent sends an email, the sent-mail folder belongs to the agent. When it creates a document, the document creator field shows the agent. The audit trail points to the agent account.
The ERP logs every invoice edit. The estimating tool logs every bid submission. The flight planner logs every weather query. Each log entry includes a timestamp, an action and a user ID. The user ID is mine. I build an agent that reviews invoices and flags discrepancies. Every flag the agent raises will log under my ID unless I provision a separate account. The log proves the action happened.
The agent has a calendar and a seat in the directory.
I provision service accounts for background jobs. The payroll worker runs under a service account. The invoice parser runs under a different one. Each account has a name. Each account has permissions. The name appears in logs. If the invoice parser makes a mistake, the log shows which account made the change. The account name is explicit. The audit trail is clear. Google made the same choice for agents. The agent holds its own identity as a coworker. The subpoena will ask for the agent's log.