Skip to main content
AWS Agent Harness cuts token costs 28% without accuracy loss, shown with a server rack and data visualization.

Editorial illustration for AWS Agent Harness Cuts Token Costs 28% Without Accuracy Loss

AWS Agent Harness Cuts Token Costs 28% Without Loss

4 min read

An agent that performs well inside Claude Code or Codex often falls apart the moment a developer tries to rebuild that same behavior with their own loop and tools. The gap sits in what's called the harness, the scaffolding around the model that handles tool calls, memory, context, and recovery when something breaks. AWS's Strands Agents team is releasing a fix for that specific problem: Strands harness, an open-source, general-purpose agent harness available now for Python and TypeScript under Apache 2.0.

The pitch is speed and cost. A single line of code, create_harness(), returns a working agent that runs on Bedrock, Anthropic, OpenAI, Google, Ollama, or LiteLLM, and it deploys either locally or to a cloud provider. AWS says it benchmarked the harness against competitors running identical Claude and GPT models across six tests, and the results point to a real efficiency gain rather than a marketing number. Before getting into what the harness actually ships with, here's how AWS frames the core result.

The Strands Agents team at AWS is targeting that gap with Strands harness, a fully assembled, general-purpose agent harness. It runs locally or deploys to a cloud provider, ships for Python and TypeScript under Apache 2.0, and starts with one line of code. The team reports 28% lower cost than other harnesses running the same Claude or GPT models across 6 benchmarks, with near-equal accuracy.

Why this matters

The HarnessTax finding is the real story here, not the 28% number. If harness choice barely moves success rates while cost can swing 5x for the same model, a lot of teams are burning budget on scaffolding, not intelligence. That reframes agent engineering as a cost problem more than a capability one, which is a different conversation than most founders are having right now.

We're glad AWS put this under Apache 2.0 rather than locking it behind a managed service, since it lets developers actually verify the savings on their own workloads instead of taking a vendor's benchmark on faith. Six benchmarks and two languages is a reasonable start, but it's not a large enough sample to call this settled, especially with a follow-up paper still pending.

For builders comparing Claude Code, Codex CLI, and now Strands, the practical move is to benchmark your own agent loop against token spend before adopting anyone's harness by default. Watch for that promised paper. Until it lands, treat 28% as a starting estimate, not a guarantee.

Common Questions Answered

What is the Strands harness and how does it address the agent scaffolding problem?

Strands harness is an open-source, general-purpose agent harness released by AWS's Strands Agents team that handles the critical scaffolding around AI models, including tool calls, memory, context, and error recovery. It solves the specific problem where agents that work well in Claude Code or Codex often fail when developers rebuild the same behavior with their own custom loops and tools, providing a fully assembled solution that runs locally or deploys to cloud providers.

What cost savings does Strands harness deliver compared to other agent harnesses?

According to AWS's testing across 6 benchmarks, Strands harness achieves 28% lower costs than other harnesses running the same Claude or GPT models while maintaining near-equal accuracy. This significant cost reduction demonstrates that harness choice can substantially impact budget efficiency without sacrificing model performance.

What programming languages and licensing does Strands harness support?

Strands harness is available for both Python and TypeScript and is released under the Apache 2.0 open-source license. This broad language support and permissive licensing make it accessible to developers across different tech stacks without vendor lock-in.

Why does the article frame agent engineering as a cost problem rather than a capability problem?

The article highlights that harness choice has minimal impact on success rates but can cause costs to swing up to 5x for the same model, indicating that many teams are burning budget on inefficient scaffolding rather than on model intelligence itself. This finding suggests that optimizing harness efficiency is a more pressing concern for most organizations than upgrading to more capable models.

How quickly can developers get started with Strands harness?

Strands harness is designed for rapid deployment, starting with just one line of code. This minimal setup requirement makes it accessible for developers who want to quickly implement an optimized agent harness without extensive configuration or scaffolding work.

LIVE23:44AWS Agent Harness Cuts Token Costs 28% Without Accuracy Loss