Google's Gemini agent gives AI coworkers their own email accounts - what it changes for business automation

Google announced its Gemini agent on 8 October at Gemini at Work 2026, and the part worth a business owner's attention is not the chat window. It is the "coworker agent": a persistent AI with its own Workspace account, its own email address on an agents subdomain, its own calendar and Drive, and an entry in your company directory. You describe the role. Gemini creates it.

Google Cloud CEO Thomas Kurian presented it as one agent behind one API that answers questions, does knowledge work, writes and runs code, and keeps working in the cloud after you close your laptop. According to Google's own announcement post, it runs in Workspace, Microsoft 365 and Slack, connects to Salesforce, ServiceNow, Jira, BigQuery, Snowflake and Postgres, and can call any MCP server inside or outside your network.

What is actually new

Agents that read your inbox are not new. OpenAI's Dots and Meta's Muse both arrived in the last month. Three things in Google's version are different.

**The agent is a user, not a feature.** A coworker agent acts under its own identity, not yours. Google says it "sees only what you share with it", and access follows the sharing and group membership your team already uses. If it edits a Doc, it shows up under its own name in version history. Every action goes into an audit trail attributed to the agent rather than to a person.

**It routes between vendors.** Google says the agent orchestrates across Gemini models and Anthropic's Claude today, picking whichever fits each job, with other models promised later. A Google product that sends some of your work to a competitor's model is a real shift. It also means you may not know which model handled a given task unless you check the logs.

**There is a hard spending cap.** You can set a per-project AI budget in the Cloud Billing Console. When it is hit, that project's agent pauses until someone resumes it. Spend is tracked per project, so it can be charged back to departments. An agent left looping overnight can burn a month's budget, and a cap that stops the agent is better than an alert email nobody reads.

What it means for a business owner

The coworker model changes how you should think about permissions. Most early agent setups ran on a person's credentials: the agent was "Sarah, but automated", with everything Sarah could see. When Sarah left, or when the agent did something odd, nobody could tell her actions from its actions.

An agent with its own account fixes that. You can give the "accounts payable assistant" access to the invoices folder and the AP inbox and nothing else. You can remove it the way you would remove a contractor. You can read its history without searching through a human's.

The workflows this suits are the ones that live entirely inside shared documents and inboxes. First-pass replies to supplier emails. Turning meeting notes into tasks in Sheets. Pulling numbers from Drive into a weekly report. Watching a shared inbox and drafting answers for a person to approve.

If your business already runs on Google Workspace, a Google spokesperson told Reworked the agent will be included in Gemini Enterprise "at no additional charge" where Gemini Enterprise is available. That could make the first experiments close to free.

The honest caveat

You probably cannot use it yet. Reworked reported that only "a limited number of companies" have access. Google's announcement gives no general release date, and we found no published pricing beyond the Gemini Enterprise comment. Treat anything you read about plans and costs as unconfirmed until Google publishes it.

Scoped access also only works if your sharing is clean. "Sees only what you share with it" assumes you know what is shared. In plenty of companies, Drive is full of folders shared with the whole domain years ago. An agent that inherits your sharing model inherits its mess.

And a demo is not production. Analysts quoted by Reworked made the same point: the real test is wide use, on messy data, over months. Multi-day tasks that write their own procedures are exactly the kind of work where small errors pile up without anyone noticing. An audit trail helps only if someone reads it.

If your core process runs outside Google's world, in a niche industry system or an on-premise database, this will not replace a purpose-built pipeline. It is strongest where the work already sits in Workspace.

What to do about it

Before access arrives, do the boring work it depends on. Pick one role you would hand to a coworker agent. Write down exactly which folders, inboxes and calendars that role needs, and nothing more. Then check who can currently see those folders. If the answer surprises you, fix the sharing now. That clean-up pays off whichever vendor's agent you end up using, including your own.