best-of-Agent-Harnesses

<!-- markdownlint-disable --> <h1 align="center"> Best of Agent Harnesses and Harness Techniques <br> </h1> <p align="center"> <strong>🏆&nbsp; Curated list of AI agent harnesses, orchestration frameworks, and harness techniques for reliable agentic systems.</strong> </p> <p align="center"> <a href="#contents" title="Project Count"><img src="https://img.shields.io/badge/projects-167-blue.svg?color=5ac4bf"></a> <a href="#for-agents" title="Agents can query this list — MCP server, llms.txt & JSON"><img src="https://img.shields.io/badge/agents-query%20this%20list-5ac4bf.svg"></a> <a href="#contribution" title="Contributions welcome"><img src="https://img.shields.io/badge/contributions-welcome-green.svg"></a> <a href="https://github.com/RyanAlberts/best-of-Agent-Harnesses/commits/main" title="Updates"><img src="https://img.shields.io/github/last-commit/RyanAlberts/best-of-Agent-Harnesses?color=green&label=updated"></a> </p> <p align="center"> 🌐 <strong><a href="https://ryanalberts.github.io/best-of-Agent-Harnesses/">Browse the searchable site</a></strong> — one page per harness, filter by capability, autonomy &amp; recovery. </p> <p align="center"> 🧰 <strong><a href="#templates-and-playbooks">Templates and Playbooks</a></strong>: copy-paste setup files and step-by-step guides for the harnesses in this list. </p> <p align="center"> 🤖 <strong>Agents can query this list</strong> — an <a href="#for-agents">MCP server</a> (<code>recommend</code>, <code>pick_harness</code>, …), <a href="llms.txt">llms.txt</a> &amp; <a href="harnesses.json">JSON</a>, so your agent recommends harnesses too. </p>

What is an agent harness?

A model answers; an agent acts. An agent harness is the runtime that turns one into the other: the model thinks, the harness decides what that thinking is allowed to touch.

Simon Willison's definition of the agent itself is the cleanest: "an LLM agent runs tools in a loop to achieve a goal." The harness is everything around that loop: which tools exist, what needs approval, what the model sees each turn, what survives a crash. Andrej Karpathy named the architecture back in 2023: the model is "the kernel process of a new Operating System", and the harness is the rest of that OS, its scheduler, permissions, and memory. The SWE-agent paper proved the stakes by coining the agent-computer interface: how tools and feedback are presented changes what a model can do, independent of the model. The field's advice has since converged on investing here rather than in framework plumbing, from Anthropic's build-simple guidance to Jerry Liu's argument that the framework era is over and the layers that matter now are skills, tools, and context quality. Those are the layers this list catalogs.

Why harnesses matter

Better models make harnesses more important: more capabilities mean more failure modes, and production needs retry logic, fallbacks, and validation. Harness quality, not just model quality, determines whether agents actually ship. This list ranks projects by relevance to harness concerns (environment, orchestration, lifecycle, guardrails) and by stars/activity.

The benchmark data now backs this up. On SWE-bench Pro, "swapping the agent harness changed pass@1 more than many model upgrades do" (AINews, Aug 8 2026, citing analysis by @joelniklaus). Same model, different harness: 23% to 52% pass@1 on GLM-5.2, and 15% to 36% on Gemma 4 26B. Harness rankings barely transfer across models (rank correlation -0.05), so a small model in the right harness can approach a much larger model in the wrong one.

The gap is widest on long-horizon work. A bare frontier model was verified at about 30% on ARC-AGI-3; Prime Agent's harness took Opus 5 to 95.5%, and the YC Paper Club talk on why the harness matters more than the model (September 2026) walks through how. The gains come from a new class of self-improving harnesses, not from piling on scaffolding: the best of them stay thin and expose only what the model cannot do for itself. And because rankings barely transfer across models, the harness choice is a pairing that must be re-asked whenever the model changes. Who says so, what they measured, and what the claim does not mean is its own page.

That is the problem the MCP server in this repo solves. Point your agent at it and it can call recommend or pick_harness to choose a harness matched to your model and task, instead of inheriting whichever harness someone else benchmarked.

The landscape at a glance

Every project in the list, plotted by adoption surface area (the simplicity ↔ capability axis) against GitHub stars. Colors are categories; the largest projects in each tier are labeled.

The same projects placed by how much unsupervised rope they're designed to give (autonomy) and what happens when a run dies (recovery). In the tables below, ★ marks headless-ready projects and ✱ marks durable ones. Both charts regenerate from the list data on every refresh.

How to Pick a Harness

Start with the guide, then the head-to-head decision pages — grounded in the same data as the tables below:

• Why the harness matters more than the model: the measurements (ARC-AGI-3 30% to 95.5% on the same weights), who says so, and what the claim does not mean
• How to pick a harness: six questions that turn this list into a decision, plus the chart to internalize first (the harness moves scores more than the model)
• How to test-drive a harness: the two-week trial protocol, with a fair setup, tasks from your own repos, seven measurements, and the walk-away test
• The best AI agent harnesses in 2026, ranked by category: the top three per category from this week's data, regenerated on every refresh
• OpenClaw vs Hermes — the always-on personal-agent debate: presence vs discipline, plus what the field reports actually say
• Managed vs self-hosted always-on agents: Grok Bot, Claude Managed Agents, QM, OpenClaw, Hermes, and OpenJarvis; who owns the computer and who pays for idle time
• Terminal coding agents — opencode vs Codex vs Gemini CLI vs crush vs goose
• Multi-agent orchestration — OpenAI Agents SDK vs CrewAI vs AutoGen vs LangGraph
• Agent memory layers — Mem0 vs Letta vs claude-mem
• Agent sandboxing: what it is, the key concepts, and the field (E2B vs Daytona vs Modal and more)
• Agent evals (SWE-bench vs inspect_ai vs Terminal-Bench)
• Eval and observability platforms (Langfuse vs LangSmith vs Braintrust vs Phoenix)
• Browser agents (browser-use vs Stagehand vs Playwright MCP vs chrome-devtools-mcp)
• Browser infrastructure (Browserbase vs Steel vs Hyperbrowser)
• Claude Code skill packs (superpowers vs GStack vs get-shit-done vs Anthropic Skills)
• Context files for agents (AGENTS.md vs CLAUDE.md vs skills vs MCP tool search)

Templates and Playbooks

The list tells you which harness to use. These tell you how to set it up. Templates are files you copy into your project; Playbooks walk you through one task, step by step.

Templates

• One AGENTS.md for every coding agent: One briefing file that Codex, Claude Code, Cursor, OpenCode, GitHub Copilot, Gemini CLI, and Aider all read, so you write your build commands, conventions, and hard rules once instead of once per tool.
• Safe Claude Code settings: permissions and a guard hook: Project settings that stop Claude Code from force-pushing, wiping work, reading secrets, or piping downloads into a shell, while leaving everyday commands alone. Two files, copy and commit.
• Minimal agent harness in Python: A working coding-agent harness in about 180 lines of Python: the loop, three tools, a permission gate, a context file, a turn budget, and a transcript you can resume after a crash. Copy it to learn how harnesses work, or as the start of your own.

Playbooks

• Build your own agent harness: Build a working coding agent in about an hour: a loop, three tools, permissions, a context file, a budget, and crash recovery, in one Python file you fully understand. You finish with the minimal harness template running on your own repo.
• Write one AGENTS.md for every coding agent: Write one briefing file that Codex, Claude Code, Cursor, OpenCode, Copilot, Gemini CLI, and Aider all read, test that each tool actually loaded it, and keep it short enough to help instead of hurt. You finish with the AGENTS.md template filled in for your repo.

Pick by use case

Reader's index: pick by what you want to do, not by category. Tag chips (e.g. ^{mcp · memory}) next to each row let you cross-filter by capability — see TAGS.md for the full cross-reference.

• I want a turnkey coding agent today — opencode, Cline, Codex, Gemini CLI, OpenHands, crush, Prime Agent · see Coding agent products (IDEs, CLIs, full suites)
• I want an always-on personal agent that lives in my chat apps — OpenClaw, Hermes, Khoj, Agent Zero, OpenHarness (HKUDS), QM, OpenJarvis · see Personal agent runtimes
• I want to extend Claude Code, Codex, or OpenCode with skills and slash commands — Anthropic Skills, wshobson/agents, superpowers, GStack, pmstack · see Coding harness configs and SDKs
• I want to build my own coding harness from scratch — [Claude Agent SDK](https://github.com/anthropics/cl