Agent Harnesses
Coding Agent InfrastructureThe canonical reading list on agent harnesses — the scaffolding that wraps LLM calls into reliable coding agents. 30 essays, papers, and podcasts covering Claude Code, Cursor, Devin, Aider, Replit Agent, MCP, and the harness-engineering discipline.
About this vault
An 'agent harness' is the production scaffolding around an LLM — the retry logic, memory store, tool dispatcher, permission gate, and telemetry pipeline that turns a raw model into something an engineer trusts to run for hours. The model is the engine; the harness is the chassis. By 2026, the gap between research demos and shipped code has collapsed onto exactly this distinction: every team building agentic coding (Anthropic's Claude Code, Cursor's Composer, Cognition's Devin, Replit Agent, OpenHands, Aider) is fundamentally competing on harness quality, not raw model intelligence. This vault collects the thirty most-cited primary sources on harness design — Anthropic's engineering posts on context engineering, tools-for-agents, managed agents, and effective harnesses for long-running work; Princeton's SWE-Agent paper that introduced 'agent-computer interface' as a discipline; Boris Cherny's Latent Space episode on why Claude Code is a Unix utility, not a product; Cursor's Composer architecture and Background Agents announcements; Cognition's Devin technical reports; Lilian Weng's foundational LLM-agent post; Karpathy's vibe-coding origin tweet and follow-up agentic-engineering thread; Harrison Chase on deep agents; Simon Willison's running architectural commentary; and Thorsten Ball's field reports from inside Zed and Sourcegraph Amp. Organized by five phases mapping the 2023-2026 evolution: from hand-rolled agent loops, through IDE-embedded autocomplete, into the Claude Code / MCP era, and now into harness comparison and long-running orchestration. Burn 451's read-later infrastructure is itself a harness pattern applied to personal knowledge — this vault is the reading list for any builder evaluating, copying, or shipping agent infrastructure.
Frequently asked questions
Who is Agent Harnesses?
Agent Harnesses is covered in this Burn 451 vault with a focus on coding agent infrastructure. The canonical reading list on agent harnesses — the scaffolding that wraps LLM calls into reliable coding agents. 30 essays, papers, and podcasts covering Claude Code, Cursor, Devin, Aider, Replit Agent, MCP, and the harness-engineering discipline.
How was the Agent Harnesses vault curated?
The Agent Harnesses vault was hand-curated by the Burn 451 editorial team from publicly available essays, blog posts, podcast transcripts, and social threads. Each piece includes an AI-generated summary so readers can triage in seconds. The vault auto-syncs as new content from Agent Harnesses is published.
How many articles are in the Agent Harnesses vault?
The Agent Harnesses vault currently contains 31 curated pieces organized by topic, not chronology. Each article has an AI summary and a direct link to the original source. Items are refreshed hourly through Burn 451's ISR pipeline, so new publications appear within a day.
How do I use this vault with Claude or Cursor?
Install the burn-mcp-server package from npm and connect it to Claude, Cursor, or any MCP-compatible AI tool. The vault becomes queryable as live context — your AI can search, summarize, and cite articles from Agent Harnesses directly in conversation without manual copy-paste or re-uploading files.
What is Burn 451?
Burn 451 is a read-later app built around a 24-hour burn timer that forces daily triage. Articles you save must be read, vaulted, or released within 24 hours. The Vault layer — including this Agent Harnesses collection — holds permanent curated reading lists for AI thought leaders, founders, and researchers.
No articles yet.
Start reading, not hoarding.
Import this vault to Burn 451 and actually read what matters.
New to Burn? See how the read-later app works →
Content attributed to original authors. Burn 451 curates publicly available writing as a reading index. For removal requests, contact @hawking520.