Red Hat, IBM, and Google announced llm-d 1.0, a Kubernetes-native distributed inference serving system that moves beyond proof-of-concept performance tricks into full production readiness. The release adds multi-tenant quality of service, zero-downtime operations, and agent-aware serving so the same endpoint can handle both human users and autonomous agents efficiently. In one test, llm-d's prefix-aware router captured 97% of available cache reuse on an agentic coding workload, and IBM/Red Hat ran 3,000 concurrent software-engineering agents for 5 to 10 times less cost than using the same model as a hosted service.
AWS has rolled out structured outputs across every Anthropic Claude model hosted on Amazon Bedrock, reaching both the standard runtime endpoint and the newer Mantle endpoint built for agentic workloads. Instead of hoping the model returns valid JSON, developers can now lock responses to an exact schema through constrained decoding, which blocks the model from generating tokens that would break the format. A companion feature, strict tool use, applies the same guarantee to function-calling arguments so agent workflows don't fail on malformed inputs.
AWS published a governance framework called Trust in Depth, designed to let AI agents operate with more autonomy while staying within enforceable limits. It combines scoping agent permissions before deployment, giving each agent a verifiable identity, enforcing boundaries at runtime via policy gateways, and observing agent behavior afterward. The framework leans on automated reasoning (mathematical proof) for rules that can be precisely defined, and human judgment for ambiguous cases, using AWS tools like Bedrock AgentCore, Guardrails, Kiro, Strands, Agent Registry and CloudWatch Omni.
Google has released Apigee hybrid 1.17.0 (September 14, 2026), adding Model Context Protocol (MCP) support that runs entirely inside a customer's own Kubernetes cluster rather than on Google-managed infrastructure. This lets organizations with data-residency or regulatory requirements turn existing OpenAPI-described APIs into AI-agent-callable tools without MCP request traffic leaving their network. The feature reuses existing Apigee identity, security policies and API product controls, and it is an optional, off-by-default capability enabled via a Helm chart upgrade.
Cohere built a controlled testbed to study how teams of coding agents should be organized, testing where work is delegated, how leads wait on workers, which models play which role, team size, and communication patterns. On ProgramBench, well-organized teams outperformed single agents by up to ~10 percentage points but at 3–7x higher cost. The key finding: delegating only exploration and planning to workers matched the performance of delegating all stages (implementation and verification too) at half the cost, and a strong lead paired with 16 cheap planning workers reached 61.8% reward versus 63.2% for an all-strong-model team, cutting cost from $510 to $155.
Orca Security built Discovery AI, an Amazon Bedrock-based agent that turns plain-English security questions into structured queries against its Sonar system, which tracks over 900 cloud resource types. Rather than relying on one large model with the full schema stuffed into every prompt, the production version splits the work across nine specialized stages and multiple foundation models. The result: dramatically lower cost, faster responses, and better accuracy on complex queries, now running live since March 2026.
AWS published a joint engineering write-up with Postman describing how Agent Mode, Postman's AI-native interface for API testing and documentation, was built to run in production at scale. Rather than model quality, the team found that tool sprawl and missing context were the biggest obstacles to reliable agent behavior. The post details architectural patterns including dynamic tool scoping, schema-based query access, dedicated context handlers, and how Amazon Bedrock provides model flexibility, cross-Region inference, data residency controls, and prompt caching.
AWS published a case study on Amazon Bedrock AgentCore payments, a managed feature that lets AI agents autonomously pay for services like model inference, one request at a time, using the x402 payment protocol. Incarna used it to let its agents pay BlockRun, a multi-provider inference router, for each individual model call, settling in USDC on the Base blockchain. AWS says Incarna cut integration time from a scoped two to three months down to three days and about 200 lines of code. During the beta, agents processed over 1,000 payments ranging from $0.001 to $0.05 per call.
Google introduced AQuA (Ambient Quality Agent), a tool that runs continuously beside production AI agents inside a Google Cloud project to find failures that don't show up in logs or health checks, such as skipped validation steps or dropped context between sub-agents. It samples production session traces, grades them against a checklist, clusters recurring failure patterns, verifies clusters against full transcripts, and tracks them over time as new, recurring, or resolved. On request, it can also trace a failure back to the exact line of code or prompt responsible, using an immutable source snapshot captured at deploy time.
Google Cloud announced the Gemini agent, a unified agent that combines chat, knowledge work, content creation, and coding into one interface accessible across devices and channels. It integrates directly inside Gmail, Docs, Sheets, Slides, Chat, and Calendar, connects to enterprise tools and databases via MCP and a tools registry, and orchestrates across multiple models — including Google's Gemini family and Anthropic's Claude — to balance quality and cost. Google also detailed security/governance features, cost controls like Smart Routing and spend caps, and shared customer results from companies like BNP Paribas, Bradesco, and Orange Spain.
Google Cloud introduced, in public preview, a remote MCP server that exposes the gcloud and bq command-line tools to AI agents via two tools: run_gcloud_command and run_bq_command. The server runs in an isolated, network-restricted sandbox on Google Cloud infrastructure, removing the need for agents to install or maintain local CLI binaries. It uses Agent Identity, OAuth 2.0, and IAM for authentication, integrates with Model Armor to screen for prompt injection, and supports Cloud Audit Logging for full visibility into tool calls.
Google announced that its Antigravity SDK now supports running agentic workflows locally and offline, with initial support for Gemma 4 26B A4B running via Google AI Edge's LiteRT. Developers can build agents that run entirely on-device, without cloud API costs or internet dependency. Google also demonstrated a hybrid 'Architect-Builder' pattern where a cloud model (Gemini 3.8 Flash) plans tasks and a local swarm of Gemma 4 26B instances does the heavy execution, keeping source code off the cloud.