@eastweb3eth: 零基础开始 Vibe Coding 必看的书---Harness 工程书 不管是 Claude 还是 Codex 已经取代了大量基础码农的工作,也让没有任何代码基础的人可以开始 Vibe Coding。但是由于没有系统学过 Harness…
摘要
本文介绍了开源的Harness工程书籍,旨在帮助零基础用户通过Claude Code和Codex进行高效Vibe Coding,详细讲解如何构建约束系统以应对AI编程模型的行为后果。
查看缓存全文
缓存时间: 2026/05/14 22:43
零基础开始 Vibe Coding 必看的书—Harness 工程书 不管是 Claude 还是 Codex 已经取代了大量基础码农的工作,也让没有任何代码基础的人可以开始 Vibe Coding。但是由于没有系统学过 Harness 工程,在使用大模型时效率很低。 现在这两本书一次把 Claude 和 Codex 的 Harness 工程一次给你解释清楚,而且还有中文版,大家不容错过~ 仓库:https://github.com/wquguru/harness-books… 感谢 @wquguru 开源。 在线阅读和下载链接:https://harness-books.agentway.dev/index.html 我是尼卡,平时会持续分享 AI、美股、Web3 相关有用又有趣的工具和项目,感兴趣的话欢迎关注,下次见~
wquguru/harness-books
Source: https://github.com/wquguru/harness-books
Harness Books
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 order is actually placed.
- If a team cannot turn individual experience into reusable rules, it will struggle to turn an agent into a stable system.
What The Two Books Focus On
Book 1: A Design Guide to Claude Code
The first book uses Claude Code as the observation target and concentrates on runtime structure. Its concern is why a system eventually has to grow components such as a control plane, query loop, tool permissions, context governance, recovery paths, multi-agent verification, and team rules.
Start with Book 1 if these are the questions you care about:
- Why harness engineering is not just prompt engineering at a larger scale
- Why prompts are fundamentally part of the control plane rather than a chat box
- Why model mistakes should be treated as a runtime norm rather than an exceptional event
- Why multi-agent work and verification should not be blended into one vague mechanism
- How a team can solidify personal experience into reusable engineering institutions
Book 2: Comparing Claude Code and Codex
The second book places Claude Code and Codex side by side and asks where each harness places order. One path starts from runtime discipline; the other starts from a more structured control layer. Both systems can work, but they distribute authority differently.
Start with Book 2 if you care more about system choice, architectural judgment, or what to learn when building your own harness:
- What the biggest control-plane divergence is between Claude Code and Codex
- How to align the roles of query loops, threads, rollouts, and state
- What governance roles are played by permissions, sandboxes, and policy languages
- How skills, hooks, and local rules encode organizational habits into the system
- If you want to build your own harness, who to learn from first and which layer to study first
Suggested Reading Paths
- Want the full frame first: read Book 1, then Book 2.
- Already familiar with coding-agent tools and want the architectural split directly: start with Book 2.
- Only want the conclusions: read Book 1 Chapter 9 plus Book 2 Chapter 7.
Full Table of Contents
Book 1 — Harness Engineering: A Design Guide to Claude Code
- Introduction
- Preface: Harness, Terminals, and Engineering Constraints
- Chapter 1 Why Harness Engineering Matters
- Chapter 2 Prompt Is Not Personality, Prompt Is the Control Plane
- Chapter 3 Query Loop: The Heartbeat of an Agent System
- Chapter 4 Tools, Permissions, and Interrupts: Why Agents Cannot Touch the World Directly
- Chapter 5 Context Governance: Memory, CLAUDE.md, and Compact as a Budgeting Regime
- Chapter 6 Errors and Recovery: An Agent System That Keeps Working After Failure
- Chapter 7 Multi-Agent Work and Verification: Managing Instability Through Division of Labor
- Chapter 8 Team Adoption: Turning a Smart Tool into a Reusable Institution
- Chapter 9 Ten Principles of Harness Engineering
- Appendix A Checklists: Turning Principles into Executable Constraints
- Appendix B Diagrams: Drawing the Runtime Skeleton
- Appendix C Source Map: Which Files Ground Each Chapter
Book 2 — The Harness Design Philosophies of Claude Code and Codex
- Introduction
- Reading Map: How to Understand Book 1 and This Comparative Book Together
- Preface: Two Harnesses, Not Accessories on the Same Horse
- Chapter 1: Why We Compare Claude Code and Codex
- Chapter 2: Two Control Planes: Prompt Assembly and Instruction Fragments
- Chapter 3: Where the Heartbeat Lives: Query Loop Compared with Thread, Rollout, and State
- Chapter 4: Tools, Sandboxes, and Policy Languages: Who Stops the Model from Moving Too Fast
- Chapter 5: Skills, Hooks, and Local Rules: How a System Learns Local Discipline
- Chapter 6: Delegation, Verification, and Persistent State: Who Prevents a System from Grading Itself
- Chapter 7: Convergence Through Different Roads, or Separate Branches
- Chapter 8: If You Are Building Your Own Harness, What to Study First
- Appendix A: Source Map That Underpins the Comparison
- Appendix B: Checklist to Determine Where Your Harness Sits
Want To Keep Practicing? Try AgentWay
|
|
AgentWay is a related but separate practice platform. Harness Books explains control structures, engineering judgments, and architectural divergences. AgentWay is where these ideas continue into training paths, drills, project exercises, and agent PoCs. |
Local Build
Build the two locale-aware Honkit sites and then assemble the unified Pages site:
python3 tools/book-kit/build_honkit.py book1-claude-code
python3 tools/book-kit/build_honkit.py book1-claude-code --locale en
python3 tools/book-kit/build_honkit.py book2-comparing
python3 tools/book-kit/build_honkit.py book2-comparing --locale en
python3 tools/book-kit/build_pages_site.py
Final output is written to dist/.
Keywords: Harness Engineering, Claude Code guide, Claude Code vs Codex, AI coding agent, control plane, query loop, agent recovery, agent verification, local governance, approval policy
相似文章
@cevenif: 用Claude Code或Codex做开发,但总觉得AI在乱跑?这门课可能正是你缺的那块拼图。 GitHub上有个开源课程叫 Learn Harness Engineering,专门教你给AI编程助手建立一套可控的工作框架,围绕五个核心机…
GitHub 上开源课程 Learn Harness Engineering,教你为 AI 编程助手(如 Claude Code、Codex)建立可控工作框架,包含12节理论课和6个实战项目,核心机制涵盖指令、状态、验证、范围、会话。
@tom_doerr: Claude Code 和 Codex 的 Harness engineering 指南 https://github.com/wquguru/harness-books…
一个 GitHub 仓库,包含两本关于 Claude Code 和 Codex 的 Harness engineering 书籍,探讨如何在真实工程环境中为编写代码的 AI 构建约束和执行方式。
@bozhou_ai: 自学 Vibe Coding 看这三个开源项目就够,不用买课 很多 AI Coding 课程的素材都从这里来,原始版本反而更系统 1. Easy-Vibe DataWhale 出品的系统教程,5k stars。分三阶段:从 AI 编程小游…
本文推荐了三个高星开源GitHub项目,帮助开发者零成本系统地学习AI编程与Vibe Coding工作流,涵盖结构化教程、提示词技能库及全方位工具目录。
@_vmlops:这是互联网上学习 harness engineering 的最佳网站 https://walkinglabs.github.io/learn-harness-engineer…
一门全面的课程,教授面向 AI 编程 agent 的 harness engineering,涵盖环境设计、状态管理和验证,使 Codex 和 Claude Code 等 agentic 编程工具更加可靠。
@Xudong07452910: 开源高质量教程推荐:《vibe-coding-cn》—— 中文 Vibe Coding 从入门到精通 这是一套中文本地化 Vibe Coding 完整教程,核心目标是帮助开发者通过 AI 结对编程工作流,把“一个想法”系统性地变成可运行的…
《vibe-coding-cn》是一份开源的中文Vibe Coding完整教程,旨在帮助开发者通过AI结对编程工作流将想法系统性地变成可运行产品,覆盖从需求拆解到部署的完整工程实践。