The leaked 1585‑line Claude Fable 5 system prompt reveals a full operating system for long‑running agents, detailing tool definitions, strict copyright limits, three‑layer file semantics, persistent artifact storage, MCP flow, and Claudeception, all enforced by hard‑coded rules.
The article traces the evolution of the "Harness" concept from traditional test harnesses to modern AI agent engineering, explains the Planner‑Generator‑Evaluator architecture, evaluates its trade‑offs, and argues that Harness Engineering is a transitional technique rather than mere hype.
The article analyzes the challenges of long‑running AI agents, showing that persistence alone is insufficient and that reliable hand‑over requires explicit specifications, external state files, drift mitigation, sub‑agents, and a verifiable evidence chain to keep the work understandable for the next model or human.
The article outlines five concrete design patterns—Checkpoint‑and‑Resume, Delegated Approval, Memory‑Layered Context, Ambient Processing, and Fleet Orchestration—that enable production‑grade, multi‑day AI agents to persist state, handle failures, and scale safely.
The author reproduces Anthropic’s long‑running harness architecture on a Codex + GPT stack, separates planner, generator, and evaluator roles, persists state to concrete artifacts, adds strict execution constraints, and demonstrates that the approach improves task success despite higher costs, while highlighting practical pitfalls and cost‑control strategies.
