{"repo":"wquguru/harness-books","free":true,"listed":false,"github":"https://github.com/wquguru/harness-books","clone":"git clone https://github.com/wquguru/harness-books.git","description":"📚 Two books on harness engineering — the design philosophies behind Claude Code & Codex: constraints, query loops, context governance, multi-agent verification. harness-books.agentway.dev","language":"Python","stars":2771,"topics":["agentic-ai","ai-agents","ai-engineering","claude-code","codex","context-engineering","developer-tools","llm","prompt-engineering"],"license":null,"category":"ai-agents","readme_excerpt":"Harness Books 中文 README Two books on harness engineering. They pursue the same engineering question: once a code-writing model is placed inside terminals, repositories, permission systems, and team workflows, what keeps the overall system bounded, continuous, and accountable for consequences? Harness Engineering: A Design Guide to Claude Code Read online · Download PDF The Harness Design Philosophies of Claude Code and Codex Read online · Download PDF These books are not meant to walk line by line through the source code. They focus on how a harness organizes constraints and execution, and how an inherently unstable model can be folded into a sustainable engineering order. Prompt layering, query loops, permission decisions, context governance, failure recovery, multi-agent verification, local rules, and team institutions together form the organ system of a harness. The real danger is not that a model occasionally says something wrong, but that the system has no structure for handling consequences. Core Claims - Harness engineering is about how constraint structures organize execution. - Once a code-writing model enters a real engineering environment, the main problem is no longer answer quality but behavioral consequences. - Prompts, tools, permissions, state, recovery, verification, and institutions are not accessories around the system. They are organs in the same control structure. - When comparing agent systems, the key question is not the feature checklist but where orde","default_branch":null,"files":null,"tree":[],"storefront":"/r/wquguru","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/wquguru/harness-books/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}