V
VocanicZ/Harness
Project-agnostic autonomous agent fleet for a GitHub-issues board
View on GitHub ↗Link checked 2026-11-14 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"vocanicz-harness": {
"command": "npx",
"args": ["-y", "github"]
}
}
}Parsed from the README we fetched on 2026-11-12; 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": {
"vocanicz-harness": {
"command": "npx",
"args": ["-y", "github"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio vocanicz-harness -- npx -y github
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 2 ★ · VocanicZ/Harness · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-13 · last seen 2026-11-14 · seen 2× · listed by 1 sources
- Score
- score 103 · 2 ★ · 1 sources · repo
- Install
npx -y github
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx -y github. 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
VocanicZ/Harness；first catalogued 2026-11-13；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.Harness
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
One orchestrator, a pool of autonomous agents, all state in GitHub.
Harness drives a pool of agent CLI sessions (Claude Code by default) against a GitHub-issues board.
Workers claim dependency-ready issues, implement, audit, test and merge them, and file new issues
for any gap they find. All state lives in GitHub (issues, labels, pushed branches) plus a small local
run directory: no database, no daemon, resumable from any host.
You grill the idea once into a PRD; the fleet does the rest.
One fleet drives one repo. HARNESS_POOL is the number of parallel issues: each pool worker runs one issue at a time. A submodule is part of that repo: its issues are filed in the main repo with a ## Code location section, not in a fleet of their own.
## Features
| Feature | Chat agent | Agent loop | Harness |
| Runs unattended | ✗ | ✓ | ✓ |
| Parallel workers | ✗ | ✗ | ✓ |
| PRD → issue breakdown | ✗ | ✗ | ✓ |
| Dependency ordering | ✗ | ✗ | ✓ |
| Independent review | ✗ | ✗ | ✓ |
| Targeted test selection | ✗ | ✗ | ✓ |
| Crash / limit recovery | ✗ | ◐ | ✓ |
| Resume on another host | ✗ | ✗ | ✓ |
| Steer mid-task | ✓ | ✗ | ◐ |
| Works without GitHub | ✓ | ✓ | ✗ |
| Zero setup | ✓ | ◐ | ✗ |
| Low token use | ✓ | ◐ | ✗ |
◐ partial. Harness steering is by injecting issues into a running fleet (/harness-issue).
Commit credit. Every commit an agent session makes ends with Co-authored-by: Harness , so GitHub shows the Harness avatar on it and lists Harness among the repo's contributors. It is added by a git wrapper on each lane's PATH, so it works for every agent CLI. Set HARNESS_COAUTHOR= (empty) in .harness/config or the environment to turn it off. Details: reference.
## Install
Ask your agent:
> install https://github.com/VocanicZ/Harness
Or run:
sh
npx -y github:VocanicZ/Harness
or, without Node:
sh
curl -fsSL https://raw.githubusercontent.com/VocanicZ/Harness/main/install.sh | bash
Agents: run the npx line above, or the curl line when git is missing, and relay any missing prerequisites to the user.
Linux, macOS and native Windows are all first-class hosts: on Windows, run either line above from Git Bash. The same
features, skills, rtdd flow and install, update, rollback and uninstall lifecycle work there, with every agent CLI
(claude, codex, opencode, copilot, hermes, openclaw, agy) running its lanes on the headless session
backend, since Windows has no tmux. It is not a reduced mode, and WSL2 is optional (run the Linux instructions inside it
if you prefer). The Windows guide covers setup, daily use, the end-to-end smoke and troubleshooting;
the parity matrix lists every feature on both. Pin a release with
HARNESS_REF=v0.1.0.
| Prerequisite | |
| node ≥ 18 | runs the installer and adds rtdd, the lane test loop. Optional with the curl line, which needs bash and curl instead; lanes without rtdd run the closest test files by hand |
| git | the npx line only: npm fetches a github: package with git, so without it npx fails before the installer runs. The curl line offers to install it |
The installer offers to install the rest: git (with the curl line), tmux, python3, curl,
sha256sum, tar and gh with your package manager (apt-get, dnf, pacman, zypper, apk or brew),
Harness drives a pool of agent CLI sessions (Claude Code by default) against a GitHub-issues board.
Workers claim dependency-ready issues, implement, audit, test and merge them, and file new issues
for any gap they find. All state lives in GitHub (issues, labels, pushed branches) plus a small local
run directory: no database, no daemon, resumable from any host.
You grill the idea once into a PRD; the fleet does the rest.
One fleet drives one repo. HARNESS_POOL is the number of parallel issues: each pool worker runs one issue at a time. A submodule is part of that repo: its issues are filed in the main repo with a ## Code location section, not in a fleet of their own.
## Features
| Feature | Chat agent | Agent loop | Harness |
| Runs unattended | ✗ | ✓ | ✓ |
| Parallel workers | ✗ | ✗ | ✓ |
| PRD → issue breakdown | ✗ | ✗ | ✓ |
| Dependency ordering | ✗ | ✗ | ✓ |
| Independent review | ✗ | ✗ | ✓ |
| Targeted test selection | ✗ | ✗ | ✓ |
| Crash / limit recovery | ✗ | ◐ | ✓ |
| Resume on another host | ✗ | ✗ | ✓ |
| Steer mid-task | ✓ | ✗ | ◐ |
| Works without GitHub | ✓ | ✓ | ✗ |
| Zero setup | ✓ | ◐ | ✗ |
| Low token use | ✓ | ◐ | ✗ |
◐ partial. Harness steering is by injecting issues into a running fleet (/harness-issue).
Commit credit. Every commit an agent session makes ends with Co-authored-by: Harness , so GitHub shows the Harness avatar on it and lists Harness among the repo's contributors. It is added by a git wrapper on each lane's PATH, so it works for every agent CLI. Set HARNESS_COAUTHOR= (empty) in .harness/config or the environment to turn it off. Details: reference.
## Install
Ask your agent:
> install https://github.com/VocanicZ/Harness
Or run:
sh
npx -y github:VocanicZ/Harness
or, without Node:
sh
curl -fsSL https://raw.githubusercontent.com/VocanicZ/Harness/main/install.sh | bash
Agents: run the npx line above, or the curl line when git is missing, and relay any missing prerequisites to the user.
Linux, macOS and native Windows are all first-class hosts: on Windows, run either line above from Git Bash. The same
features, skills, rtdd flow and install, update, rollback and uninstall lifecycle work there, with every agent CLI
(claude, codex, opencode, copilot, hermes, openclaw, agy) running its lanes on the headless session
backend, since Windows has no tmux. It is not a reduced mode, and WSL2 is optional (run the Linux instructions inside it
if you prefer). The Windows guide covers setup, daily use, the end-to-end smoke and troubleshooting;
the parity matrix lists every feature on both. Pin a release with
HARNESS_REF=v0.1.0.
| Prerequisite | |
| node ≥ 18 | runs the installer and adds rtdd, the lane test loop. Optional with the curl line, which needs bash and curl instead; lanes without rtdd run the closest test files by hand |
| git | the npx line only: npm fetches a github: package with git, so without it npx fails before the installer runs. The curl line offers to install it |
The installer offers to install the rest: git (with the curl line), tmux, python3, curl,
sha256sum, tar and gh with your package manager (apt-get, dnf, pacman, zypper, apk or brew),
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/vocanicz-harness/)
- Source
- github · https://github.com/VocanicZ/Harness
- Browse by field
- Open source
- Traction
- 2 ★
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.