How The Harness Works

The harness is powered by Strands Agents, the open-source agent framework from AWS. Each user session runs in its own microVM with isolated CPU, memory and filesystem, which AWS argues prevents cross-session data leakage in stateful agent workflows. The platform is model agnostic, with AWS documentation describing support for models served through Amazon Bedrock alongside OpenAI and Google Gemini, and the ability to switch providers mid-session by changing a configuration parameter rather than rewriting orchestration logic.

The design is deliberately layered. Teams that outgrow the configuration interface can export their agent to Strands code and continue running it on the same platform with the same isolation and deployment pipeline. AgentCore retains support for LangGraph, LlamaIndex and CrewAI, so the harness coexists with rather than replaces existing framework choices.

The companion AgentCore CLI brings infrastructure-as-code workflows to agent deployment, with current support for AWS CDK and Terraform support coming soon. A new persistent filesystem allows agents to suspend mid-task and resume later, which addresses one of the more awkward gaps in long-running agent workflows including human-in-the-loop approvals and asynchronous tool calls. Coding agent skills, prebuilt guidance modules tuned for AgentCore, are available now for Kiro and rolling out to Claude Code, Codex and Cursor by the end of April. AWS says there is no separate charge for the harness, CLI or skills, with customers still paying for the underlying AgentCore capabilities and model and resource usage.

Market Position

The release lands in a crowded field. Google has folded its agent tooling into the Gemini Enterprise Platform, Microsoft is positioning Azure AI Foundry as the orchestration layer for Copilot deployments and OpenAI continues to evolve its Assistants and Responses APIs. The platforms differ on dimensions that matter to enterprise buyers including region availability, supported frameworks, model-provider neutrality, sandboxing model, persistence, identity integration, observability and pricing basis. AWS is making a notable bet on framework neutrality, supporting third-party orchestrators alongside its own Strands framework while keeping the underlying execution surface proprietary.

Customer signals are limited. AWS's launch blog quotes Brazilian commerce platform VTEX on the harness, and separate AWS customer materials reference Parrot Analytics and others, but AWS has not published broad adoption metrics, latency benchmarks or cost-per-session data for the new harness. That makes head-to-head comparison with Vertex AI or Azure AI Foundry difficult at this stage.

Practical Limitations

The harness ships in preview in only four regions, which restricts data-residency-sensitive deployments in jurisdictions including Canada, Brazil, India and most of Europe outside Frankfurt. Configuration-driven agents also hit a complexity ceiling. AWS itself notes that custom orchestration logic, specialized routing and multi-agent coordination require switching from configuration to code-defined harness, which means the three-API-call promise applies cleanly to single-agent use cases rather than the orchestration-heavy patterns enterprises are increasingly building.

There is also a portability question. While the harness supports multiple models and frameworks, the runtime including the microVM isolation model, the persistent filesystem and the session lifecycle is specific to AgentCore. Teams that adopt the harness without abstracting their tool definitions and prompts risk lock-in to AWS even when their model choice remains flexible. The CLI's initial reliance on AWS CDK ahead of Terraform may also slow adoption among shops standardized on multi-cloud tooling.

Strategic Implications

For technology leaders, the announcement sharpens a procurement question that has been gathering force for months. Building agent infrastructure in-house, an option many enterprises pursued during the early generative AI cycle, is increasingly difficult to justify when hyperscalers are absorbing the orchestration layer with no separate charge for the harness itself. The decision is shifting toward which managed runtime aligns with existing data, identity and compliance controls.

The harness also signals that AWS sees agent platforms, not foundation models, as a durable source of differentiation. By holding the execution surface while remaining permissive about models and frameworks above it, the company is positioning AgentCore as a foundational primitive for agentic workloads that enterprises consume rather than build. Whether that bet pays off depends less on the harness itself than on how quickly AWS expands regional coverage, publishes operational benchmarks and demonstrates the harness in workloads beyond developer demos.