A new research paper introduces Mage-VL-Cowork, a 4B parameter computer-use agent that combines GUI interaction with code and terminal execution. By utilizing a new synthetic data framework called Mage-CUA-Forge, the developers reduced per-task training expenditure by 82.6% while reaching 66% on the OSWorld-Verified benchmark.
Amazon Bedrock AgentCore now supports Session endpoints, allowing developers to view and interact with web applications live as an AI coding agent builds them. By routing traffic through an authenticated, isolated microVM session, changes appear in the browser instantly without requiring separate deployments.
NVIDIA introduced NemoClaw, an open blueprint framework designed to combine agent harnesses with optimized Nemotron models and secure runtimes. It enables developers to deploy agents that are governed by strict security policies while maintaining high performance on owned infrastructure.
Google has transitioned its Computer Use tool to general availability within the Gemini API ecosystem. This feature allows models to interact with computer interfaces to perform tasks, now supported for production use across Interactions and GenerateContent APIs.
Amazon has enabled intent-driven UI automation by pairing Nova Act with the Bedrock AgentCore Browser Tool. This setup allows engineering teams to define test workflows through natural language instructions instead of maintaining rigid, selector-heavy codebases.
MoEngage successfully integrated over 400 internal REST APIs as agent tools using Amazon Bedrock AgentCore Gateway. This approach eliminated the need for manual MCP server maintenance, complex networking, and security risks associated with public internet exposure.
Google Cloud has released IAM Helper, a suite of agent-facing building blocks designed to automate complex Identity and Access Management (IAM) workflows. By integrating with Google Cloud's core IAM engines via MCP (Model Context Protocol), these tools enable autonomous agents to handle tasks like troubleshooting 403 errors, simulating policy impacts, and requesting just-in-time access.
This research introduces a verification-based framework that refines multimodal emotion reasoning in AI agents. Instead of retraining models, the system identifies specific component failures and applies targeted prompt updates to improve performance.
Anthropic has launched a beta API for Claude Enterprise, allowing administrators to programmatically manage Claude settings across Slack channels and workspaces. This release enables reading and modifying tagging configurations and managing Access bundles via new /v1/organizations/claude_tag/ endpoints.
Amazon Bedrock AgentCore is a new service designed to streamline the deployment and management of multi-agent architectures. It handles agent hosting, secure tool access via MCP, and session isolation, enabling teams to focus on agent behavior rather than operational overhead.
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.
NVIDIA has published OpenShell, an open-source runtime that treats agent workloads as untrusted and grants access to files, tools and systems only when needed. It pairs with the new NVIDIA Vera CPU and, optionally, BlueField-4 DPUs with NVIDIA Sentry for hardware-enforced monitoring. NVIDIA says this combination forms a full reference architecture for running autonomous agents safely at data-center scale.
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.