no_human

From ticket to reviewed pull request.
Free and open-source, on your machine.

English · 简体中文 · 日本語 · 한국어

getnohuman.com · Quickstart · Docs · Watch it work a sprint

_{▶ Watch the loop — a ticket in, a reviewed pull request out; the whole loop in 57 seconds.}

The AI coding factory you can trust:

• A plan before any code, from the ticket plus what it finds in your repo. When planning fails, the coder is told it is working without one; when the change is judged trivial the plan is skipped without telling the coder, by design — the skip is still stated in the run's event stream.
• An adversarial review. A different model, in a session that never saw the coder's transcript, told to refute "done". You get a pass/fail checklist citing file and line — never a numeric self-score.
• A tamper guard. Deleted tests, new skips, an assertion turned into a tautology — counted mechanically before the review gate runs, then justified against your acceptance criteria or the attempt stops.
• Proof the fix fixed the bug. The tests offered as evidence must fail at the merge base and pass on the new tree — the reproduction gate runs both. Out of the box that binds a Python bug fix; repro_gate.mode: required binds every kind and every change.
• Your tests run, locally and optionally through your CI — and a PR that found no test command says NOT RUN on its face.
• An honest stop. When it cannot finish it stops and says why — a specific question when your answer would unblock it, a structured record when it has simply run out of budget — never an invented plausible diff.

Install

One line (CLI + board)

uv tool install no-human   # or: pipx install no-human — the wheel ships the board
nh init && nh doctor       # token, config, first repo; then prove the install is real

Desktop app

Each release ships a SHA-256 alongside the artifact. Platform notes and the first-run walk-through: docs/quickstart.md.

From source

git clone https://github.com/no-human-ai/no_human.git && cd no_human
uv sync                 # installs the `nh` entry point into .venv
(cd web && npm install && npm run build)   # builds the board (cold first install can take minutes)
uv run nh init          # token, config, first repo (about 2 minutes)
uv run nh doctor        # verify the install is real before relying on it

The web build is not optional if you want the board: a source checkout ships no web/dist, so without it nh start serves the API only and renders no UI. Needs Python 3.12+, uv, git, and Node with npm for the board build.

Product highlights

A plan before any code Acceptance criteria you can check, written from the ticket and your repo.
An independent reviewer A second model that never saw the coder's session, told to refute "done". Pass or fail; every finding that blocks cites file and line.
Your tests, on the PR's face Run locally or through your CI. No test command found reads NOT RUN, never blank.
A tamper guard Deleted tests, new skips and tautological assertions are counted before review. Unjustified, the attempt stops.
Proof the fix fixed the bug The tests offered as evidence must fail on the old code and pass on the new. The gate runs both, and the event log shows the verdict.
An honest stop When it needs you, it parks with one specific question instead of guessing.
Your tracker's tickets, on your board Pick Jira or Linear tickets from the backlog (monday.com boards are polled). Each one is scoped with you before it starts.

_{Stills: the real board on a demo workload.}

Run one task

Run nh with no arguments for the shell: your lanes, a live event tail, and an intake you describe a task to in plain English. Every command below still works.

nh                                   # the shell
nh start                             # board + worker on 127.0.0.1:8420
nh task add https://github.com/org/repo/issues/42 --repo ~/git/repo
nh status                            # needs-you / working / waiting / done
nh review <id>                       # the reviewer's evidence checklist
nh diff <id>                         # the diff it wants to ship
nh approve <id>                      # your approval squash-lands the PR (git.approve_identity)
nh reject <id> --reason "..."        # send it back with feedback

Integrations

Point no_human at the tracker you already use and it pulls the tickets to your board — a tracker's filter lives in your config, never in a task's own text, and a transport error logs and retries on the next tick instead of crashing the pool.