Repo Harness

repo-harness

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 hc (herdr-core) >= external_tooling.herdr_core.min_version 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.

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.

Install hc through Herdr.app or a herdr-core release. Verify that hc --version
reports at least .ai/harness/policy.json#external_tooling.herdr_core.min_version.
Persistent review hosting requires POSIX process groups; on Windows use WSL.
Missing, unusable or older hc 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

Pi is an…