Four Harnesses, Four Philosophies

_{Guest contributor: Janakiram MSV is principal analyst at Janakiram & Associates, an independent analyst and advisory firm focused on cloud-native infrastructure, platform engineering, and agentic AI. He writes for Forbes, The New Stack, and Forward Future.}

Every serious AI agent platform in 2026 is running the same handful of frontier models from Anthropic, OpenAI, and Google. Same APIs, same context windows, same benchmarks. And yet some of these platforms ship reliable production agents in weeks while others spend nine months in prototype hell. The model has stopped being what separates them.

What separates them now is the operating system wrapped around the model, a layer the industry has started calling the agent harness, and it has quietly become the most consequential part of the AI stack. That operating system has a name. It is called the agent harness, and it has quietly become the most consequential layer in the AI stack.

The companies winning in production AI right now, Anthropic, OpenAI, Amazon, and a noisy open-source community, have shifted their gravity accordingly. They have stopped competing on raw model access and started competing on the thing that wraps the model. The scaffolding that turns a stateless text generator into something that can read files, run shell commands, browse the web, persist memory across sessions, and recover when a tool call fails halfway through. Get the harness decision wrong, and you will spend a year rewriting orchestration code while your competitors ship.

An agent harness is the runtime infrastructure surrounding a language model that handles everything the model cannot do on its own. The model can reason about a task, but it needs the harness to actually carry one out. Anthropic's engineering team puts it plainly. The Claude Agent SDK, they say, is "a powerful, general-purpose agent harness adept at coding, as well as other tasks that require the model to use tools to gather context, plan, and execute". A LangChain engineer coined a cleaner formulation that has caught on. "If you're not the model, you're the harness."

The mental model is straightforward. The language model is the CPU, and the harness is everything else, the file system, the network stack, the shell, the scheduler. In practice, a harness manages the agent loop, orchestrates tools, decides what context to keep and what to compact, persists state across sessions, enforces guardrails like timeouts and step limits, recovers from failed tool calls, and logs everything for debugging and evaluation.

LangChain demonstrated this dependency in a way that should have ended the "model is the product" conversation for good. Same model, same weights, different harness. Their deepagents-cli coding agent jumped from 52.8 percent to 66.5 percent on Terminal-Bench 2.0, which the team described as moving from outside the Top 30 into the Top 5. The intelligence stayed exactly where it was. All of that gain came from better scaffolding.

The interesting part is not that harnesses exist. The interesting part is that the major AI providers have each made very different bets about what a harness should be. The four examples below sit at different maturity levels, from generally available SDK to limited preview to community project, but together they map the design space the industry is converging on.

Anthropic released Claude Managed Agents in public beta on 8 April 2026. You define the model, the system prompt, the tools, the MCP servers, and the skills. Anthropic runs the agent loop in its own managed environment, complete with prompt caching, context compaction, and a secure execution sandbox.

What is striking about this product is who is selling it. The model lab itself is now in the harness business. Anthropic's own engineering writing shows that Claude's agentic performance depends heavily on harness assumptions, and that those assumptions can become stale as models improve. By offering the harness as a managed product, Anthropic is selling the full performance envelope of its model, not just the API. The Claude Agent SDK is the open-source companion, exposing the same harness that powers Claude Code in Python and TypeScript libraries for teams that want to run it in their own infrastructure. Both products carry the same message. Anthropic now treats the harness as part of the model's value, and it intends to own that layer rather than leave it to someone else. 

Amazon took a different route. Amazon Bedrock AgentCore launched its Managed Harness in preview on 22 April 2026. AWS describes the architecture cleanly. "Every agent has an orchestration layer which contains the loop that calls the model, decides which tool to invoke, passes results back, manages context windows, and handles failures. Running that loop requires infrastructure underneath it ... This infrastructure forms the agent harness."

AgentCore Managed Harness lets a developer define an agent in three API calls. Pick a model, write a system prompt, list the tools. AWS handles compute, microVM sandboxing per session, identity, VPC networking, memory, and observability. What AWS does differently is multi-model from day one. The harness supports Bedrock, OpenAI, and Google Gemini, and can switch providers mid-session without losing context. Rather than bet on a single model winning, AWS is betting that the harness is where lock-in happens, and that owning the harness gives them durable customer ownership regardless of which model wins.

AWS then went a step further. On 28 April 2026, AWS and OpenAI announced Bedrock Managed Agents powered by OpenAI, a separate limited-preview product built around what AWS calls the OpenAI agent harness, packaged with AWS security, identity, and data residency. That phrasing is worth reading twice. Amazon is now reselling OpenAI's harness, with the two companies announcing it jointly. The harness has become a tradable asset.

OpenAI's harness story changed materially on 15 April 2026 with the next evolution of the Agents SDK. What used to be a relatively thin orchestration library is now a model-native harness with native sandbox execution, configurable memory, Codex-like filesystem tools, support for MCP and AGENTS.md, and a Manifest abstraction for describing the agent's workspace. Developers can plug in sandboxes from Blaxel, Cloudflare, Daytona, E2B, Modal, Runloop, or Vercel, or bring their own.

OpenAI's own framing of the update is revealing. They name three existing trade-offs explicitly. "Model-agnostic frameworks are flexible but do not fully utilize frontier models capabilities; model-provider SDKs can be closer to the model but often lack enough visibility into the harness; and managed agent APIs can simplify deployment but constrain where agents run and how they access sensitive data." The new SDK closes all three gaps at once.

This sits underneath AgentKit, the broader developer suite OpenAI launched at DevDay 2025, which packages Agent Builder for visual workflows, ChatKit for embeddable UI, and Evals for tracing and quality. The combined story is now a developer journey, not a single runtime. Start in Agent Builder with drag-and-drop, ship a chat UI with ChatKit, drop down to the Agents SDK for code-level control, and ride the same harness all the way to production. The practitioner consequence is portability. With the April 2026 release, OpenAI has effectively answered Claude Agent SDK with a comparable model-native harness, while keeping the visual-builder and embeddable-UI layers as a parallel funnel. Once your workflow lives in Agent Builder, your UI lives in ChatKit, and your runtime lives in the Agents SDK sandbox, leaving OpenAI stops being a simple model swap and becomes a full re-platforming exercise. OpenClaw: The Harness as a Community Artefact

OpenClaw is one of the more visible open-source harnesses operating outside the major labs. It runs autonomous agents on top of Claude, GPT, Gemini, or local models, and ships with messaging-channel integrations for Telegram, Discord, Slack, and WhatsApp. The community has built layers on top of it. AlphaClaw bundles a self-healing watchdog, Git-backed rollback, and a browser-based dashboard. The OpenClaw Harness repo adds a structured Sprint plan-build-review-iterate-ship pipeline, modelled on how human engineering teams actually work.

The wider open-source harness ecosystem is maturing fast around it. Hermes Agent, released by Nous Research in February 2026, has crossed 27,000 GitHub stars and now ships with an explicit OpenClaw migration command. That a community project considers cross-harness portability a first-class feature tells you the harness layer is now mature enough to have switching costs worth migrating away from.

OpenClaw matters for two reasons. Its design philosophy is community-driven rather than vendor-driven, and its growth has been visible enough that Anthropic adjusted its subscription policy in response. In April 2026, Anthropic restricted OpenClaw and other third-party agent harnesses from Claude subscriptions, citing capacity and caching inefficiencies. In May, Anthropic reversed the restriction and introduced a separate Agent SDK credit tier. Users got their access back. Anthropic got billing protection. The OpenClaw episode is a useful tell. The harness layer is now important enough that subscription economics have to be redesigned around it.

Three things follow from this shift.

First, the harness is where your switching costs are going to live. Models are increasingly interchangeable for many enterprise tasks, but harnesses are not. If your agent's logic lives in an Agent Builder visual workflow, or in a Claude Managed Agent configuration, or in an AgentCore harness manifest, the portability question is no longer "which model" but "which platform". Pick deliberately.

Second, the choice between managed and open-source harness is not analogous to the managed-versus-self-hosted database call. A managed harness gets you to a working prototype in three API calls and an afternoon. An open-source harness gets you control over how the agent loop actually behaves, which matters when you are debugging why an agent burned through 400,000 tokens to write one PR.

Third, the model lab's harness will probably always perform best on its own model. Anthropic's own engineering writing emphasises that harness assumptions are tightly coupled to model behaviour, which is why third-party harnesses sometimes show regressions even when the model upgrade should help. If you are running Claude in production at scale, the Claude Agent SDK or Claude Managed Agents will likely outperform a generic open-source harness on the same task. The cost of that performance is platform commitment.

The reason the harness story is bigger than it looks is that it inverts the assumed direction of AI value capture.

For the last three years, the working theory has been that the model labs sit at the top of the stack and capture most of the value, while infrastructure providers and application developers split the rest. That theory assumed the model was the scarce resource and everything else was a commodity.

In 2026, the labs are racing to ship harnesses, and the hyperscalers are racing to resell them, because everyone has realised the same thing. The harness is what turns a model into a product. The harness is where the orchestration code, the tool integrations, the memory schemas, and the operational know-how accumulate. Frontier model quality still matters, but for many production agent workloads, switching costs are moving upward from the model API into the harness.

If you are placing AI infrastructure bets in 2026, the question is no longer which model is best for your use case. It is whose harness you want to commit to for the next three years, because that decision will quietly outlast the next several model generations and shape everything you build on top of it.