Summary
AWS's Bedrock AgentCore Agent Registry — the governed catalog for agents, tools, skills, and MCP resources first previewed in April 2026 and moved to a dedicated agent-registry namespace on August 6, 2026 — is now generally available. In the same release, AWS added auto-detection through AWS Organizations so AgentCore Runtimes and Gateways across member accounts are automatically discovered and cataloged into a single registry. AgentCore Evaluations also expanded to evaluate agents built with TypeScript versions of supported frameworks.
What changed
AWS Agent Registry graduated from preview to GA inside Amazon Bedrock AgentCore, adding an AWS Organizations auto-detection integration that finds and catalogs every AgentCore Runtime and Gateway in member accounts into one central registry. Bedrock AgentCore Evaluations now supports agents built with TypeScript versions of supported frameworks.
Why it matters
Enterprise agent sprawl — many teams shipping many agents through many accounts — has been the missing platform primitive on AWS. GA plus org-wide auto-detection turns 'how many agents do we have and who owns them' into a query rather than a spreadsheet, which is exactly the visibility security and platform teams needed before signing off on production. It also puts AWS's answer to Cloudflare's Agent Cloud (Cloudflare Mesh, Agent Memory) on the map at the same governance layer, using the AWS Organizations trust boundary customers already run for IAM and Control Tower.
Evidence excerpt
Amazon Bedrock AgentCore Evaluations now evaluates agents built with TypeScript versions of supported frameworks, and AWS Agent Registry is now generally available. AWS Agent Registry's launch introduced auto-detection with AWS Organizations to automatically discover and catalog AgentCore Runtimes and Gateways across your organization's member accounts into a single registry.