AWS just commoditized the agent harness. Your orchestration layer is now a config file.

Amazon Bedrock AgentCore harness is now generally available.

Two API calls. CreateHarness to define. InvokeHarness to run.

Your agent gets a sandboxed microVM, filesystem, shell, built-in memory, skills, browser, code interpreter, and unified observability. No orchestration code. No container builds. No wiring.

Here is what most teams miss: the harness is model-agnostic.

You can plan with Claude Opus, switch to GPT-5.5 for code execution, then swap to Gemini for summarization. Context survives the transition. The conversation continues. Provider lock-in just died.

Built-in memory is provisioned automatically: semantic + summarization strategies, 30-day event expiry, multi-tenant isolation. No second API call. No ARN to remember.

Skills load from four sources: AWS-curated catalog with a single toggle, Git repos pinned to commits, S3 bundles, or local paths. Your agent picks up domain expertise on demand instead of improvising.

The graduation path is what matters most.

One CLI command exports your harness to Strands-based code. Same compute, same primitives, same observability. Configuration you start with is the configuration you operate at scale. When custom orchestration is needed, you export to code on the same platform without rebuilding.

A/B testing ships with statistical significance reporting per session. Immutable versions. Named endpoints for rollback. The feedback loop from idea to validated agent is now minutes, not weeks.

Audit your agent deployment stack today. If you are still wiring memory, observability, and tool access by hand, you are burning engineering cycles on infrastructure AWS just made managed.

The agent framework market is no longer about orchestration primitives. It is about what runs underneath them.

SOURCE: https://aws.amazon.com/blogs/machine-learning/amazon-bedrock-agentcore-harness-is-now-generally-available-go-from-idea-to-production-grade-agent-in-minutes/
VERIFIED: AWS Blog (June 18, 2026), AWS What's New (June 17, 2026), AWS Documentation
SIGNAL: AWS just turned agent harness from a build problem into a configure problem. Every team still hand-wiring orchestration is now competing against a managed primitive.
---