Gemini coworker agents get email and Drive: onboard them like hires

Google Cloud used its Gemini at Work 2026 keynote on October 8 to announce a single "universal" Gemini agent, plus Gemini coworker agents that get their own Workspace account. That means an email address, a calendar, Drive storage and a spot in the company directory. The agent stops being a chat box and starts being a staff member. Staff members need onboarding.

What actually happened

Per Google's announcement, delivered by Google Cloud CEO Thomas Kurian:

• One agent, many surfaces. The Gemini agent runs on web, iOS, Android, Windows, Mac, the command line, Google Workspace, Microsoft 365 and Slack. It runs in the cloud, so work continues for hours or days after you close the laptop.
• Coworker agents with persistent roles. You create one by describing the role. It gets an address on an agents subdomain, its own calendar and Drive, and it shows up in version history under its own name. You can @mention it in Chat or tag it in a doc comment.
• Access by sharing, not inheritance. Google says a coworker agent sees only what people explicitly share with it. Each agent has a cryptographically attested identity, and every action goes to an audit log.
• Agent Gateway. An "AI network firewall" applies one policy set to all traffic in, out and between agents.
• Cost controls. Smart Routing picks a model per workload by performance and cost. Hard per-project spend caps pause the agent when hit. Claude models are available inside Gemini today, per Google.

What Google did not give: general-availability dates, pricing for the agent, or a self-serve SMB tier. VentureBeat also notes that Google has not said how customers turn the universal agent on, or how provisioning and licensing will work.

Why Gemini coworker agents matter for your business

An inbox is an attack surface. Give an agent an email address and it can get phishing, vendor invoices and password-reset links. Decide before launch what it may open, forward and reply to.

Sharing becomes your permission system. If access follows what you share, a lazy "share the whole folder" hands the agent your payroll sheet. Make one Drive folder per agent role and share into it on purpose.

Set the budget before the agent starts. A per-project cap that pauses the agent is the right default. Put each agent in its own project so one runaway job cannot spend the whole month.

Write the job description. An agent defined as "help with events" will do too much. "Books vendors under $500 from this approved list" is a role you can audit.

Sources: Google Cloud, VentureBeat.