Enterprise AI
Google Cloud Adds Grok 4.6 as a Preview, Not a Default
Google Cloud's August 28 roundup says Grok 4.6 is available in Preview on Gemini Enterprise Agent Platform, with text and image input, reasoning, function calling, and structured output. The listing expands model choice; it does not make Grok the platform default or publish independent quality, safety, latency, cost, residency, or production-readiness results.
Citation-ready: Google Cloud listed Grok 4.6 in Preview on Gemini Enterprise Agent Platform for text and image input, reasoning, function calling, and structured output during the week ending August 28, 2026.
What happened and why it matters
No. It adds a selectable preview model to the platform's Model Garden; builders still need explicit model configuration, policy review, workload evaluation, fallback, and release evidence.
Official Google Cloud weekly product roundup
Primary reference: Google Cloud: What's new with Google Cloud. Kaleido Field checked the event date and the article's attributed facts against this source.
| Source date | August 28, 2026 roundup for August 24-28 |
|---|---|
| Checked by Kaleido Field | August 31, 2026, 09:04 CST |
| Source function | current enterprise-model analysis separating preview availability, supported input and output modes, model choice, production controls, commercial terms, and independent workload evidence |
A model catalog is an option surface
Adding a model can let a team compare reasoning behavior, tool use, image input, latency, and cost without moving the whole application. It can also add another set of terms, limits, and failure patterns.
A deployment record should name the exact model label, platform status, region, endpoint, prompt version, tools, structured schema, safety settings, data policy, fallback, and approval owner.
The roundup leaves evaluation open
The short listing does not publish a benchmark, pricing table, latency distribution, safety report, or production service level for this integration. Model-family adjectives should therefore remain vendor positioning.
Teams should run representative tasks and keep invalid outputs, tool errors, image failures, policy blocks, timeouts, retries, fallback results, and human dispositions rather than reporting only successful examples.
Evidence boundary
Official availability facts: Preview status, platform, Model Garden family position, and named capabilities. Google and xAI positioning: model suitability for coding, agents, and knowledge work. Not established: default selection, general availability, regional coverage, pricing, quotas, data retention, safety behavior, independent quality, latency, uptime, or suitability for a specific enterprise workflow.
FAQ
What is the release state?
Preview on Gemini Enterprise Agent Platform.
What inputs and outputs are named?
Text and image input, reasoning, function calling, and structured output.
Is it the default model?
The official roundup describes availability in Model Garden, not default selection.