Google Gemini Enterprise Agent Launch

Google says each job on its new agent 'runs on a model fitting the task at hand' - simple tasks route to Gemini Flash, complex work goes to Google's frontier model Argon, and 'Anthropic PBC Claude models are also available today' ^[1]. That's a striking admission from a company that spent years building Gemini as Claude's direct rival. Constellation Research analyst Holger Mueller called this open, multi-model design the real differentiator: 'What stands out is the open approach - which allows enterprises to use already trusted and purchased LLMs as part of the automation scope of Gemini agent' ^[2]. Independent analyst Carmi Levy frames the strategic logic bluntly - by separating the agent from the underlying model, Google 'allows enterprises to use whatever model makes sense' ^[3]while still owning the orchestration layer customers actually touch. One Reddit commenter put it more cynically, calling Google's willingness to route to Claude 'the most honest feature announcement in the AI race so far' - the implication being that the value sits in the data and the harness, not the model underneath. The bet is that even IT teams who prefer Claude for raw model quality will still route their workflows, governance, and billing through Google, making Google the toll booth regardless of which model wins the underlying race.

Beyond a single chatbot, the Gemini agent can spin out temporary and persistent 'coworker' sub-agents, each with 'their own dedicated identities and expertise, with their own @agents.company.com emails and their own persistent storage' ^[1], coordinating workflows across parallel and sequential steps that can run for hours or days. That only works if enterprises trust it with sensitive systems, so Google paired the feature with governance: every sub-agent inherits identity and audit controls, and admins can 'set hard limits on AI spend within the Cloud Billing Console,' enforced by monitoring token usage ^[1]. Info-Tech Research Group's Mahmoud Ramin reads this as containment rather than elimination of risk - a permissioned sub-agent system is 'much more contained' than an unrestricted autonomous agent with broad system access ^[3]. But Computerworld's framing of Carmi Levy's analysis leaves the harder question open: whether CIOs and CISOs will actually trust a multi-day, self-directed process - one with its own email address - running unattended inside Salesforce, Jira, or a production database ^[3].

The timeline is its own tell. Gemini launched as a model family in December 2023; by February 2024 Google had already retired the 'Duet AI' branding and folded Workspace's enterprise AI into Gemini Business and Gemini Enterprise tiers ^[4]. In April 2026, Google launched the Gemini Enterprise Agent Platform at Cloud Next, merging Vertex AI and agent lifecycle tooling with a new Salesforce partnership ^[5]. Now, barely six months later, that framing has been replaced again by a 'single universal agent.' Each iteration promised to be the definitive enterprise AI entry point. That repetition surfaced immediately in community reaction: Reddit commenters mocked the absence of a concrete release date - 'coming as soon as possible,' 'Very Soon(TM)' - and compared it to past slow Google AI rollouts, while others pointed to ongoing complaints that the existing Workspace Gemini forgets context after roughly 20 prompts, a reliability gap the new agent's marketing doesn't directly address.

Google leaned on scale to justify urgency: nearly 80% of Google Cloud customers are actively using its AI products, and close to 500 enterprise customers have each individually processed over 1 trillion tokens on the platform in the past year ^[2]. Separately, Google says nearly 90% of Fortune 100 companies now use Gemini Enterprise ^[6]. Alongside the general-purpose agent, industry-specific versions for financial services and legal are already in preview, with government, healthcare, and retail editions 'coming soon' ^[8]. Yet the company has not published pricing, a firm general-availability date, or details on how existing Workspace admins actually enable the feature. Futurum Group frames the underlying strategy as putting 'the agent ahead of the model' ^[7]- the product, not the LLM underneath, is what Google wants enterprises bound to. Until the access mechanics and cost are public, though, that positioning remains aspirational rather than something IT buyers can act on today.