A
Ancienttwo/repo-harness
File-backed workflow harness for reliable Claude Code and Codex sessions
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 最终跳转到 github.com
安装与配置
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"ancienttwo-repo-harness": {
"command": "npx",
"args": ["-y", "repo-harness@latest"]
}
}
}解析自我们于 2026-11-01 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"ancienttwo-repo-harness": {
"command": "npx",
"args": ["-y", "repo-harness@latest"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio ancienttwo-repo-harness -- npx -y repo-harness@latest
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- ★ 数取值
- 435 ★ · Ancienttwo/repo-harness · 取自该仓库的 GitHub 页面 · （2026-11-13 20:00:50 核对）
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型：开源项目
- 收录与活跃
- 收录于 2026-11-02 · 最近见到 2026-11-14 · 共见到 13 次 · 被 1 个来源列出
- 评分构成
- 综合分 104 · 435 ★ · 1 个来源 · repo
- 安装
npx -y repo-harness@latest
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
npx -y repo-harness@latest。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: 开源项目。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
Ancienttwo/repo-harness；我们收录于 2026-11-02；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# repo-harness
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
### Shared context, hooks and review evidence for Claude and Codex
English | 简体中文 | 日本語 | Français | Español
Give the agent a GitHub issue and acceptance checks. Keep changes and verification evidence in its PR.
repo-harness ships a CLI, skills and hooks for context, review evidence and
handoffs. The GitHub issue and PR own task identity, scope and status. Repository
files let Claude and Codex resume work across sessions.
## Contents
Get Started
Why repo-harness
Task Authority
Key Features
How It Works
Task Workflow
Work Across Sessions
Hooks
Local Human Control Board
MCP Connector
Reviewing Work
Skills
Maintainer Reference
Acknowledgements
Current Release
License
## Get Started
### 1. Install the CLI
Prerequisites: a Git working tree, bun, and usable herdr >=0.9.5 for host readiness; macOS/Linux also require bash,
while Windows requires Git for Windows (including its Bash and usr/bin
tools). jq is optional. No Node.js required — the installer uses Bun >=
1.4.0 as the runtime, installing or upgrading Bun first when needed.
bash
# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/Ancienttwo/repo-harness/main/install.sh | sh
# Windows (PowerShell)
irm https://raw.githubusercontent.com/Ancienttwo/repo-harness/main/install.ps1 | iex
With Bun >= 1.4.0 already on PATH, skip the shell installer. Package-manager-owned
Bun installs fail closed with the matching upgrade command (brew upgrade bun)
instead of overwriting manager-owned files.
bash
bunx repo-harness@latest install # Bun one-shot bootstrap
bun add -g repo-harness # or install the persistent CLI first
repo-harness install
npx -y repo-harness@latest install # npx fallback; the CLI still runs on Bun
Install herdr from herdr.dev and verify herdr --version.
Persistent review hosting requires POSIX process groups; on Windows use WSL.
Missing or unusable herdr blocks host readiness. Before upgrading from tmux,
drain existing reviewers using the previous version and explicitly rebind terminal
endpoints. See runtime cutover.
### 2. Bootstrap the host runtime
bash
repo-harness install
Pi is an optional host under the default --target both. When pi is on
PATH, install and update register the installed repo-harness directory with
pi install . An existing user package entry is retained.
Missing Pi skips this step. Preview with repo-harness install --dry-run --json.
The minimum Pi version is MINPIVERSION; there is no upper bound.
repo-harness setup check and repo-harness update --check report the version,
path resolver capability, package entry and skill projection.
Catalog skills use ${PICODINGAGENTDIR:-$HOME/.pi/agent}/skills and the
same profile selection and ownership rules as the other hosts. Uninstall removes
only owned package entries and unchanged owned skills. Package commands use Pi's
CLI; repo-harness does not write Pi settings, credentials or trust files.
Pi covers session context, agent notices, edit/write, bash and Stop hooks.
It has no fleet roles or subagent hooks. PowerShell, !/!! user shell,
other extensions' file writes and third-party MCP writes are outside this coverage.
DSH (DeepSeek Harness) is a package host. repo-harness ships a Cordis plugin
and a bundle patch; DSH manages the installation. Load the plugin with
English | 简体中文 | 日本語 | Français | Español
Give the agent a GitHub issue and acceptance checks. Keep changes and verification evidence in its PR.
repo-harness ships a CLI, skills and hooks for context, review evidence and
handoffs. The GitHub issue and PR own task identity, scope and status. Repository
files let Claude and Codex resume work across sessions.
## Contents
Get Started
Why repo-harness
Task Authority
Key Features
How It Works
Task Workflow
Work Across Sessions
Hooks
Local Human Control Board
MCP Connector
Reviewing Work
Skills
Maintainer Reference
Acknowledgements
Current Release
License
## Get Started
### 1. Install the CLI
Prerequisites: a Git working tree, bun, and usable herdr >=0.9.5 for host readiness; macOS/Linux also require bash,
while Windows requires Git for Windows (including its Bash and usr/bin
tools). jq is optional. No Node.js required — the installer uses Bun >=
1.4.0 as the runtime, installing or upgrading Bun first when needed.
bash
# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/Ancienttwo/repo-harness/main/install.sh | sh
# Windows (PowerShell)
irm https://raw.githubusercontent.com/Ancienttwo/repo-harness/main/install.ps1 | iex
With Bun >= 1.4.0 already on PATH, skip the shell installer. Package-manager-owned
Bun installs fail closed with the matching upgrade command (brew upgrade bun)
instead of overwriting manager-owned files.
bash
bunx repo-harness@latest install # Bun one-shot bootstrap
bun add -g repo-harness # or install the persistent CLI first
repo-harness install
npx -y repo-harness@latest install # npx fallback; the CLI still runs on Bun
Install herdr from herdr.dev and verify herdr --version.
Persistent review hosting requires POSIX process groups; on Windows use WSL.
Missing or unusable herdr blocks host readiness. Before upgrading from tmux,
drain existing reviewers using the previous version and explicitly rebind terminal
endpoints. See runtime cutover.
### 2. Bootstrap the host runtime
bash
repo-harness install
Pi is an optional host under the default --target both. When pi is on
PATH, install and update register the installed repo-harness directory with
pi install . An existing user package entry is retained.
Missing Pi skips this step. Preview with repo-harness install --dry-run --json.
The minimum Pi version is MINPIVERSION; there is no upper bound.
repo-harness setup check and repo-harness update --check report the version,
path resolver capability, package entry and skill projection.
Catalog skills use ${PICODINGAGENTDIR:-$HOME/.pi/agent}/skills and the
same profile selection and ownership rules as the other hosts. Uninstall removes
only owned package entries and unchanged owned skills. Package commands use Pi's
CLI; repo-harness does not write Pi settings, credentials or trust files.
Pi covers session context, agent notices, edit/write, bash and Stop hooks.
It has no fleet roles or subagent hooks. PowerShell, !/!! user shell,
other extensions' file writes and third-party MCP writes are outside this coverage.
DSH (DeepSeek Harness) is a package host. repo-harness ships a Cordis plugin
and a bundle patch; DSH manages the installation. Load the plugin with
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/ancienttwo-repo-harness/)
- 来源
- github · https://github.com/Ancienttwo/repo-harness
- 按领域浏览
- 开源项目
- Traction
- 435 ★
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。