notes: What is an Agent Harness 卡

[joyehuang]

Earendil 四组件定义 + translation layer 用户主权论 + 三方材料对照（Zechner/Glukhov/dsh 源码）+ 谱系分化判断。

止步 PR 不合并。bun run check 0 errors。

---

Summary by cubic

Adds a Chinese reference note on "Agent Harness" from Earendil's blog post, covering the four components, the soul document comparison, and a four-source cross-check: Zechner's critique, Glukhov's review, DeepSeek Harness source, and our own pi stack practice. Also fixes the neon type assertion in SiteStats.astro so bun run check passes cleanly on branches cut from main; no runtime behavior changes.

^{Written for commit f689097. Summary will update on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
blog	Ready	Preview	Sep 3, 2026 3:08am UTC

[cubic-dev-ai]

1 issue found across 2 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/content/notes/0926-what-is-an-agent-harness.md">

<violation number="1" location="src/content/notes/0926-what-is-an-agent-harness.md:15">
P2: The relatedNote `0926-deepseek-harness-internals` does not exist in the notes collection, and the body repeatedly cross-references it as a「同主题卡」(DeepSeek Harness 源码调研、见同主题卡). The notes page (`src/pages/notes/[...id].astro`) filters relatedNote entries against the live `getCollection('notes')` set, so this dangling id is silently dropped — the「Related Notes」card never renders and there is no link to the promised deep-dive. Either add the note or remove the dead references.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

P2: The relatedNote 0926-deepseek-harness-internals does not exist in the notes collection, and the body repeatedly cross-references it as a「同主题卡」(DeepSeek Harness 源码调研、见同主题卡). The notes page (src/pages/notes/[...id].astro) filters relatedNote entries against the live getCollection('notes') set, so this dangling id is silently dropped — the「Related Notes」card never renders and there is no link to the promised deep-dive. Either add the note or remove the dead references.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At src/content/notes/0926-what-is-an-agent-harness.md, line 15:

<comment>The relatedNote `0926-deepseek-harness-internals` does not exist in the notes collection, and the body repeatedly cross-references it as a「同主题卡」(DeepSeek Harness 源码调研、见同主题卡). The notes page (`src/pages/notes/[...id].astro`) filters relatedNote entries against the live `getCollection('notes')` set, so this dangling id is silently dropped — the「Related Notes」card never renders and there is no link to the promised deep-dive. Either add the note or remove the dead references.</comment>

<file context>
@@ -0,0 +1,62 @@
+status: ready
+source: https://earendil.com/posts/what-is-a-harness/
+relatedNote:
+  - 0926-deepseek-harness-internals
+  - 0326-harness-engineering-codex-production-practice
+draft: false
</file context>

[cubic-dev-ai]

1 existing issue remains and 1 new issue found across 1 file (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/content/notes/0926-what-is-an-agent-harness.md">

<violation number="1" location="src/content/notes/0926-what-is-an-agent-harness.md:92">
P3: The expansion added a fourth comparison perspective (视角四：我们自己的日常) and a fourth material, but the surrounding framing still says 「三方」. Line 82 heading 「## 三方对照：同题不同答」, the frontmatter description 「三方材料对照（…我们自己的 pi 栈实践）」, and 核心内容's 「三个视角各占一角」 now all contradict the four 视角 blocks below. Rename these to 四方/四个视角 so the structure matches the content.</violation>
</file>

<sub>Requires human review: Auto-approval blocked because this review re-detected 1 unresolved issue already reported by Cubic.

Re-trigger cubic</sub>

[cubic-dev-ai]

P3: The expansion added a fourth comparison perspective (视角四：我们自己的日常) and a fourth material, but the surrounding framing still says 「三方」. Line 82 heading 「## 三方对照：同题不同答」, the frontmatter description 「三方材料对照（…我们自己的 pi 栈实践）」, and 核心内容's 「三个视角各占一角」 now all contradict the four 视角 blocks below. Rename these to 四方/四个视角 so the structure matches the content.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At src/content/notes/0926-what-is-an-agent-harness.md, line 92:

<comment>The expansion added a fourth comparison perspective (视角四：我们自己的日常) and a fourth material, but the surrounding framing still says 「三方」. Line 82 heading 「## 三方对照：同题不同答」, the frontmatter description 「三方材料对照（…我们自己的 pi 栈实践）」, and 核心内容's 「三个视角各占一角」 now all contradict the four 视角 blocks below. Rename these to 四方/四个视角 so the structure matches the content.</comment>

<file context>
@@ -19,44 +19,87 @@ draft: false
-- **Mario Zechner 的锐评**（pi 作者的另一篇）和 **Glukhov 的 Pi Review**（独立评测博主，评测过多个 harness）：从用户视角看 harness 的差异——扩展生态、记忆方案、上下文管理的取舍
-- **DeepSeek Harness 源码调研**（我们的完整源码审阅，见同主题卡）：从实现视角看 harness 能做到什么程度——「一切皆插件」到主循环自己都是一行配置、事件日志作为唯一真相源。它证明四组件之上还有整整一层「harness 的自我工程化」空间
-- **我们的日常实践**：pi 的扩展 + Telegram 桥 + 记忆注入 + skills，就是在「拥有并改装 harness」这个论断上的 everyday practice——translation layer 让我们可以在 OpenRouter / Command Code 之间按成本与稳定性路由模型，这正是作者说的「自由与选择」的日常形态
+**视角四（我们自己的日常）**：pi 的扩展 + Telegram 桥 + 记忆注入 + skills，就是「拥有并改装 harness」这个论断的 everyday practice。最有说服力的一条：translation layer 让我们可以在 OpenRouter / Command Code 之间按成本与稳定性路由模型（8 月底 GLM 延迟毛刺排查 → 切换路由的整个过程），这正是作者说的「自由与选择」的日常形态——不是口号，是出问题时你有第二条路可走。
 
 ## 当前理解 / 结论
</file context>