Google 發布通用 Gemini 代理,為每個代理配專屬 Workspace 帳號與審計軌跡Google launches universal Gemini agent, giving every agent its own Workspace account and audit trail
- 事件
- Google Cloud 於 10 月 8 日 Gemini at Work 2026 發布 Gemini 代理,用戶只須描述目標,代理即自行規劃、選模、連接業務系統並交付成品;每個「同事代理」獲發專屬 Workspace 帳號、電郵、日曆與公司通訊錄身份,行動寫入審計日誌,並可選用 Anthropic 的 Claude 模型。At Gemini at Work 2026 on 8 October, Google Cloud launched the Gemini agent: users describe an objective, and the agent plans the work, selects models, connects to business systems and returns finished output. Each "coworker agent" receives its own Workspace account, email address, calendar and directory identity, actions land in audit logs, and Anthropic's Claude models can be selected alongside Gemini.
- 背後
- Google 自四月推出 Agent Platform、九月強化 Workspace 自動化後,此番把重心由「讓開發者造代理」轉為「讓每位員工有一個常駐代理」,並以跨平台記憶與代理閘道搶佔企業編排層;以模型中立換取企業不必綁定單一供應商。After launching its Agent Platform in April and expanding Workspace automation in September, Google has shifted from helping developers build agents to giving every employee one persistent agent. With cross-platform memory and an Agent Gateway it is contesting the enterprise orchestration layer, trading model-neutrality for vendor lock-in relief.
我們認為,真正的賣點不是代理能力,而是可審計的身份。當代理擁有公司帳號、電郵與目錄身份,它就不再是工具,而是需要入職、授權與離職流程的組織成員。企業應先問:誰是它的主管?誰覆核它的對外通訊?In our view the real selling point is not agent capability but auditable identity. Once an agent holds a corporate account, email and directory presence, it stops being a tool and becomes an organisational member that needs onboarding, authorisation and offboarding. The first question for enterprises is: who manages it, and who reviews its outbound communications?
- 對日常工作的影響
- 對 IT 主管而言,代理身份將納入 IAM 與目錄管理,需新增生命週期流程;對法務而言,代理以公司名義發出的文件與郵件須有明確授權紀錄;對人力資源而言,需在職責表內區分人與代理的覆核責任。For IT leaders, agent identities now enter IAM and directory management and require a new lifecycle process. For legal teams, documents and emails sent in the company's name by an agent need a clear authorisation record. For HR, job descriptions must distinguish human versus agent review responsibility.
- 如何改善
- 本週先盤點三個最常被要求自動化的流程,寫明代理可自主執行到哪一步、哪一步必須停下來等人批准,並把這條界線寫進系統提示詞,而非留在同事的口頭默契裡。This week, pick the three workflows most often requested for automation and write down exactly which step an agent may execute autonomously and which step must stop and wait for human approval — then encode that boundary in the system prompt rather than leaving it to informal team assumptions.
