探秘 Claude Code,搞懂 Agent Harness|对谈来新璐
Summary
This Shizilukou Crossing episode interviews Lai Xinlu of Share AI about Agent Harness design, using Claude Code and Learn Claude Code as the main teaching sample. Lai defines harness as the model-external system that gives an agent execution ability, context, state, memory, permissions, and orchestration. The discussion argues for model-aligned harness design: stronger models should get more context and action capacity with less brittle programmatic control, and CLI/Unix-like interfaces may be more agent-native than prompt-node or flow-graph frameworks.
Key Claims
- Agent Harness can be understood as “everything outside the model”: tools, runtime environment, context, state, memory, permissions, and multi-agent governance.
- Lai breaks harness design into three layers: execution ability, context/environment, and governance/orchestration.
- The execution layer includes files, search, browser operation, language interpreters, CLI tools, code-registered tools, and MCP-like extensions, but the episode argues that CLI often outperforms newer abstractions because models have more pretraining exposure to Unix and shell patterns.
- The context/environment layer includes system prompts, AI Skills, Persistent Agent Memory, context-window management, compression, and cross-agent handoff documents.
- The governance/orchestration layer controls multi-agent roles, information access, and permissions, such as giving exploration agents read-only capabilities so they cannot mutate code or tests.
- Claude Code is presented as an especially instructive harness because of its memory update hooks, AutoDream-like consolidation, markdown memory files, context compression, and task handoff mechanisms.
- Good harnesses should fit the model’s operating logic and remain orthogonal to model improvement; a harness that over-controls the model may become a bottleneck as models improve.
- K Computer represents Share AI’s lightweight Unix-style approach: a virtual computer built as data structures rather than a traditional Docker-like sandbox.
- The entrepreneurial direction extends beyond coding tools into hybrid agent networking, agent payment, personalized model training, and agent-native organizations such as “zero-person companies.”
Key Quotes
“模型以外都是 Harness” — Lai’s compact definition of agent harness.
“模型才是 Agent” — the reason the episode emphasizes model capability before harness cleverness.
“更多 context、更少 control、更多 action 能力” — the preferred direction for Claude Code-style harness design.
“CLI is all you need” — the Unix/CLI-oriented interface thesis.
“最好的管理就是不要做管理” — the warning against context management that fights the model’s own operating pattern.
Connections
- Lai Xinlu — guest explaining harness layers, Claude Code lessons, and Share AI’s infrastructure thesis.
- Share AI — company behind Learn Claude Code and the K-series agent infrastructure tools.
- Claude Code and Learn Claude Code — central sample used to study memory, skills, tools, compression, and handoff design.
- Agent Harness — core concept added by this source.
- K Computer — concrete Share AI implementation of a lightweight Unix-style agent work environment.
- Agent-Facing Interfaces, Headless Software, and Agentic Workflow — existing wiki concepts sharpened by the CLI/Unix-first argument.
- Context Engineering, Persistent Agent Memory, and AI Skills — context and self-improvement layer inside the harness.
- Subagent Workflow and Model Harness Co-Evolution — multi-agent and model-harness design frames extended by the episode.
- Anthropic, Manus, MiniMax, and Youyou Agent — reference points used to compare models, agent products, memory/sandbox approaches, and future agent-native experiments.
- Agentic Economy — future-facing infrastructure frame for agent payment, hybrid networking, personalized training, and agent economic actors.
Contradictions
- No direct contradiction with prior wiki content. The source reinforces the existing Headless Software, Agent-Facing Interfaces, Persistent Agent Memory, and Model Harness Co-Evolution threads while making a stronger claim that CLI/Unix-style surfaces may be more natural for current agents than newer protocol or flow-graph abstractions.