AWS announced general availability of training sessions within Amazon SageMaker AI serverless model customization. Teams can write their own post-training loops — including custom loss functions and reward signals for reinforcement learning — while SageMaker AI handles GPU allocation, distributed execution, fault recovery, and checkpoint storage. Supported techniques include SFT, DPO, RLVR, RLAIF, and multi-turn RL, and users can choose LoRA or full fine-tuning. The feature supports models including gpt-oss-20b, gemma-4-31B-it, Qwen3.6-27B, and Qwen3.8-27B, and billing is based on tokens processed, pausing while a user's reward function scores responses.
Google announced Public Preview of streaming support in API Gateway, covering Server-Sent Events, chunked/NDJSON responses, WebSockets and gRPC streaming. Streaming endpoints can now sit behind the same gateway as regular APIs, keeping existing authentication, logging and monitoring, without any changes to the API spec. Streams can stay open up to one hour, and gateways now get a predictable default hostname instead of a generated hash. The feature also ties into model routing, letting a single gateway stream responses from Gemini, Claude and OpenAI gpt-oss models.
AWS published a walkthrough for the Adaptive Agentic Intelligence Framework (AAIF), built on Strands Agents, which routes simple requests to small local models (via Ollama) and only sends complex requests to cloud models through Amazon Bedrock. A lightweight 1B-parameter model (llama3.2:1b) acts as an orchestrator deciding where each request should go, with an example IoT monitoring agent that uses local telemetry retrieval, local vision analysis, and cloud-based expert insights. AWS states that in the hybrid setup, roughly 80 percent of traffic can be handled locally without hitting a paid API, and the architecture can run fully on edge hardware (e.g. Raspberry Pi with 8GB memory), fully in the cloud, or in a hybrid mode.
Google has added an Extension System to its Agents CLI (from v1.5.0, with a first-party LangChain extension in v1.8.0) that lets developers override or add CLI commands without forking the tool. Previously, Agents CLI's deployment, evaluation and observability pipeline was tightly coupled to Google's own Agent Development Kit (ADK); now teams can scaffold, run, deploy and evaluate LangChain, LangGraph or Deep Agents projects through the same command surface. Extensions are distributed as directories in Git repositories, pinned to a commit SHA in a lockfile, and can be installed at project or user scope. The system also lets enterprise platform teams wrap commands like deploy with custom policies, such as compliance scans or SSO gates. The feature is marked experimental in v1.8.0.
Google Cloud has made Anthropic's Claude Opus 5.5 and Claude Sonnet 5.5 selectable inside its Antigravity agentic coding platform, alongside Gemini 3.8 Flash and Gemini 4 Argon. Developers can switch between model families mid-conversation across Antigravity 2.0, the CLI, and IDE extensions for VS Code, JetBrains and Visual Studio, all under one enterprise billing and security boundary. Google also describes two engineering patterns: using a second model family to independently review code written by the first ('LLM-as-a-judge'), and assigning fast Gemini Flash subagents to handle high-volume mechanical tasks while a stronger model handles deep reasoning.
AWS introduced Agent Registry, a managed catalog service for Model Context Protocol (MCP) servers, agents, and agent skills. Instead of hardcoding every tool into an orchestrator, agents can now search an approved, versioned catalog at runtime and build a client from the returned descriptor. A reference sample demonstrates a Discover → Instantiate → Execute loop using Amazon Bedrock AgentCore Gateway and AgentCore runtime, with Anthropic Claude Sonnet as the foundation model.
Eon, a data protection ISV running on AWS, replaced per-tool credentials and local MCP servers with a single Amazon Bedrock AgentCore MCP Gateway. The gateway uses Cedar-based policies to enforce least-privilege access for both human engineers and an autonomous SRE agent running Claude on Amazon Bedrock, routing calls to MCP servers hosted on AgentCore Runtimes across multiple AWS accounts. Developer onboarding time dropped from about two days to about two minutes after rolling the system out to 100+ developers and roughly 10,000 sessions.
AWS and Keyfactor published a reference design that fixes a known weak point in Model Context Protocol (MCP) deployments: MCP has no built-in way to authenticate which agent is actually making a request. The architecture adds three trust layers — user-to-system, agent-to-agent, and agent-to-tool-server — built on signed request envelopes, delegation assertions signed by the user, RFC 8693 audience-restricted tokens, and live OCSP revocation checks. A working example runs on Amazon Bedrock and the AWS Strands Agents SDK with Keyfactor EJBCA issuing and validating the X.509 certificates, and the full code is on GitHub.
IBM Research's ALTK-Evolve extracts short behavioral rules from an agent's own training-task attempts and appends them to the system prompt of a basic ReAct agent running on GPT-4.1. On the τ²-bench customer-service benchmark (retail and airline domains), this learned-memory approach raised accuracy and reliability without updating model weights or using human annotation. The full 'lossless' guideline set pushed a GPT-4.1 agent to a retail Pass^4 score of 67.5%, topping the October 12, 2026 leaderboard snapshot, including beating a model fine-tuned specifically on synthetic retail data. The technique also improved a frontier GPT-5.5 agent on airline tasks, taking it to the top of that leaderboard as well.
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.
Google Cloud published a reference architecture for building AI agents that coordinate long-running, GPU-heavy scientific tasks like protein folding and compound screening, which break standard single-LLM-agent setups due to timeouts and context overflow. The design separates a cognitive orchestrator (Gemini on Agent Runtime) from a GPU execution layer (NVIDIA NIMs like ESMFold and GenMol on GKE) and wraps both in an enterprise governance plane with agent identity, a gateway, a registry and Model Armor. It also lays out best practices such as passing bulky data by reference instead of inline, streaming progress updates, and gating irreversible actions behind human approval.
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.
Anthropic rolled out a beta tracing feature that exports OpenTelemetry spans from both the Messages API and Claude Managed Agents sessions. Developers using the Claude SDK can now capture these spans natively in seven languages: Python, TypeScript, C#, Go, Java, PHP, and Ruby. Enabling the feature requires setting up a destination for the telemetry data inside the Claude Console.
NVIDIA published a case study showing how Siemens EDA applied its open NeMo Gym evaluation library to tighten up an agentic tool used for chip characterization. Instead of checking individual tool calls, the team scored complete final output files with a domain-specific verifier, then used the failure patterns to rewrite the agent's skill instructions and MCP tool descriptions. After several rounds of this loop, a composite accuracy benchmark climbed from roughly 55% to 95%, while the agent needed far fewer steps and far less output to get there. The experiments relied on about 25 evaluation rollouts running Claude Opus 4.8 as the agent model inside Claude Code.
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.
Anthropic has introduced a beta option on its Claude Platform that allows a Managed Agents agent to construct its own workflow for large, multi-part jobs, such as going through hundreds of documents. Instead of handling everything in one pass, the agent splits the task into phases, delegates pieces across multiple sub-agents, and merges their output into a single result. The job is handed off to the server, which executes it asynchronously and reports progress through a stream of events.
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.
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 has released the Developer Knowledge API, a structured, machine-readable source for Google Cloud, Firebase and Android documentation aimed at AI agents and developer tooling. Instead of scraping web pages or relying on an LLM's training cutoff, agents and CLIs can now query fresh, Markdown-formatted docs through several interfaces: a gcloud CLI surface, an installable agent skill, client libraries, and a browser-based API explorer. The underlying index is refreshed frequently so retrieved answers stay close to the latest published documentation.
AWS released a step-by-step walkthrough showing how to give Claude Desktop (on Amazon Bedrock) live internet access through Amazon Bedrock AgentCore Gateway, closing the gap left by the model's training cutoff. The setup wires AWS IAM Identity Center SSO through Amazon Cognito as a SAML-to-OAuth federation layer, issuing JWTs that the AgentCore Gateway validates on every request. The Web Search capability itself is MCP-compatible and runs on an internal Amazon web index covering tens of billions of documents, so no query traffic leaves AWS and no third-party API key is needed. The feature is currently limited to three AWS Regions: us-east-1 (N. Virginia), eu-west-1 (Ireland), and ap-northeast-1 (Tokyo).