Ancienttwo/repo-harness

File-backed workflow harness for reliable Claude Code and Codex sessions

Before you install: no copy-paste command · license MIT · link reachable

First step: npx -y repo-harness@latest install # npx fallback; the CLI still runs on Bun

View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · redirects to github.com

Install & config

Client config (built from the install command this repo gives)

{
  "mcpServers": {
    "ancienttwo-repo-harness": {
      "command": "npx",
      "args": ["-y", "repo-harness@latest"]
    }
  }
}

Parsed from the README we fetched on 2026-11-01; we have not executed it.

command/args come from the install command the repository states. When it is ambiguous, the project README wins.

VS Code (.vscode/mcp.json - the key is servers)

{
  "servers": {
    "ancienttwo-repo-harness": {
      "command": "npx",
      "args": ["-y", "repo-harness@latest"]
    }
  }
}

Same server, but VS Code keeps it under <code>servers</code>.

Claude Code (command line)

claude mcp add --transport stdio ancienttwo-repo-harness -- npx -y repo-harness@latest

Claude Code does not read a config file; add the server with this command.

Key names differ by client: Clients & CLI

Star count: 435 ★ · Ancienttwo/repo-harness · read from the repository page · (checked 2026-11-13 20:00:50)
Source: read directly from its GitHub page · type: open-source project
Harvest history: first seen 2026-11-02 · last seen 2026-11-14 · seen 13× · listed by 1 sources
Score: score 104 · 435 ★ · 1 sources · repo
Install: npx -y repo-harness@latest

FAQ (answers come from our records)

How do I install it?

The repository provides this install command: npx -y repo-harness@latest. It comes from the repository itself; we cannot guarantee it runs as-is in your client.

Who is it for?

We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.

Who maintains it?

repository Ancienttwo/repo-harness；first catalogued 2026-11-02；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.

# 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

Listed badge (optional)

Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.

[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/ancienttwo-repo-harness/)

Source: github · https://github.com/Ancienttwo/repo-harness
Browse by field: Open source
Traction: 435 ★
added: today

More like this

llm-agents-radarOpen-source project sepehrkeyhani00/bashoor-ai-menuOpen-source project relaticle/relaticleOpen-source project

All 1,671 →

Filed under

Open source1,671 entries Open-source repo2,514 From GitHub2,437

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index