Navigation Explore Code Guide
The Four Layers
| Layer | Responsibility | Does not replace |
|---|---|---|
| Model | Proposes text and tool calls | Permission and recovery |
| Runtime harness | Runs the loop and tools | Repository contract |
| Repository harness | Instructions, state, verification | Runtime loop |
| Orchestrator | Coordinates runtimes and sessions | Each runtime’s decisions |
An orchestrator can launch several runtimes without owning their loops. A repository can improve its contract without changing runtime.
Choose in the Right Order
- Define the task and acceptable autonomy.
- Select a runtime that owns the required loop.
- Write the repository contract: instructions, pass criteria, verification.
- Add an orchestrator only when coordination, isolation, or recovery across tasks requires it.
Four Sources, Four Uses
| Source | Used to | Limit |
|---|---|---|
| Strict comparison | Identify runtimes | Not a universal ranking |
| Orchestrator table | Compare coordination | Not a runtime |
| Best of Agent Harnesses | Explore 160 projects, 12 categories | 2026-08-23 snapshot |
agent-harnesses.json | Read provenance and evidence | unknown is not none |
Short Trial, Traceable Verdict
Compare two or three candidates on real tasks in separate worktrees. Measure human verdict, interventions, plan drift, wall time, accepted-task cost, recovery, and setup friction.
Links: Agent Harness Map · Agent Harness Engineering · Agent Tools · Glossary
Enter your email to read the full card and get the complete PDF bundle.
All content is free and open-source. We just ask for your email.