From ticket to reviewed pull request. Free and open-source, on your machine.
- ✓Open-source license (MIT)
- ✓Actively maintained (<30d)
- ✓Clear description
- ✓Topics declared
- ✓Documented (README)
- !Install pipes a remote script into a shell (curl | sh)
git clone https://github.com/no-human-ai/no_human && cp no_human/*.md ~/.claude/agents/Subagents overview
<div align="center">
<img src="docs/assets/nh-mark.png" alt="" width="140" height="140">
# no_human
<!-- mcp-name: io.github.no-human-ai/no_human -->
**From ticket to reviewed pull request.**<br>***Free and open-source, on your machine.***
[](https://github.com/no-human-ai/no_human/releases/latest) [](https://github.com/no-human-ai/no_human/actions/workflows/ci.yml) [](https://www.python.org/) [](LICENSE)
[getnohuman.com](https://getnohuman.com) · [Quickstart](docs/quickstart.md) · [Docs](docs/README.md) · [Watch it work a sprint](https://getnohuman.com/demo)
[](https://github.com/no-human-ai/no_human/releases/latest) [](https://getnohuman.com/) [](https://getnohuman.com/)
<a href="https://getnohuman.com/"><img src="docs/assets/hero-loop-poster.jpg" alt="The no_human board: one task waiting on a question in Needs answer, four tasks working in parallel, one pull request ready for review." width="880"></a>
<sub>▶ <a href="https://getnohuman.com/">Watch the loop</a> — a ticket in, a reviewed pull request out; the whole loop in 57 seconds.</sub>
</div>
The AI coding factory you <ins>**can trust**</ins>:
- **A plan before any code**, from the ticket plus what it finds in your repo.
- **An adversarial review.** A different model, fresh context, read-only tools,
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 — blocked before a reviewer token is spent.
- **Proof the fix fixed the bug.** For a bug fix, the tests offered as evidence
must fail at the merge base and pass on the new tree — the reproduction gate
enforces that, and you can require it for every change.
- **Your tests run**, locally and optionally through your CI.
- **An honest stop.** When it cannot finish, it parks with one specific question
instead of inventing a plausible diff.
## Install
Whichever way you install, you need a **Claude credential**: an OAuth token
from `claude setup-token` (personal subscription or enterprise), so install the
Claude Code CLI first — `npm install -g @anthropic-ai/claude-code`, or
`curl -fsSL https://claude.ai/install.sh | bash`. The desktop app also calls
that CLI for every task. To pay Anthropic directly instead, set
`llm.auth_mode: "api_key"` and put your `ANTHROPIC_API_KEY` in
`~/.no_human/.env`.
### One line (CLI + board)
```bash
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
[](https://github.com/no-human-ai/no_human/releases/latest) [](https://getnohuman.com/) [](https://getnohuman.com/)
Each release ships a SHA-256 alongside the artifact. Platform notes and the
first-run walk-through: [docs/quickstart.md](docs/quickstart.md).
### From source
```bash
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](https://github.com/astral-sh/uv), git, and Node with
npm for the board build.
## 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.
```bash
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.
| Tracker | How tickets arrive | Filter you configure |
|---|---|---|
| **Jira Cloud** | Polled via REST `search/jql` (HTTP Basic `email:token`) | `integrations.jira.jql` |
| **Linear** | Polled via the GraphQL API | `integrations.linear.team_key` + `state_types` + `label` |
| **monday.com** | Polled via GraphQL v2 | `integrations.monday.board_id` + `status_column` + `todo_labels` |
With write-back on (`write_back`, off by default), the ticket moves with the
task — matched by status category, type, or the label you name, never a
hard-coded transition id — and gets the PR link; a task that needs a human is commented on, never
transitioned. GitHub and
GitLab issues import as tasks by URL, and PRs or MRs open on your own host;
Slack and Teams get a message when a task needs you; Jenkins and CircleCI can
run your test layers and gate the loop. Setup for each:
[docs/adapters.md](docs/adapters.md).
**Watch the Jira flow end to end** — tickets synced from a Jira board, scoped,
implemented, and delivered as a review-passed pull request (click for the full
video with every step):
[](https://getnohuman.com/assets/demo-jira.mp4)
<p align="center">▶️ <strong><a href="https://getnohuman.com/assets/demo-jira.mp4">Play the full demo</a></strong> — 1:33, from Jira board to review-passed PR</p>
## MCP server — hand it work from the agent you are already in
no_human ships an **MCP (Model Context Protocol) server**: a stdio bridge, built
on the official Python MCP SDK, that lets Claude Code, Cursor or any MCP client
file work with your local no_human and check on it.
```bash
nh mcp-serve # the MCP server, over stdio
```
Two tools, and no more:
| Tool | What it does |
|---|---|
| `task_add(title, description, repo_path)` | Files a task. no_human then plans it, writes the change, runs your tests, has a second model review it, and opens the pull request. |
| `task_status(task_id_or_external_id)` | Returns that task's current state — status, attempts, the PR link once there is one. |
It talks to your own no_human at `http://127.0.0.1:8420` and nothing else: no
auth, because that address is localhost, and no service of ours in between. For
Claude Code, the same server ships as a plugin — point it at
[`plugins/no-human/`](plugins/no-human/) and the two tools appear in your
session.
```jsonc
// .mcp.json
{ "mcpServers": { "no_human": { "command": "nh", "args": ["mcp-serve"] } } }
```
## Docs
| | |
|---|---|
| [quickstart.md](docs/quickstart.md) | Zero to first task, per platform |
| [configuration.md](docs/configuration.md) | Every setting and default |
| [verification.md](docs/verification.md) | The gates, the bounded loop, the limits |
| [security.md](docs/security.md) | Auth boundary, the never-merge rule, guards |
| [blockers.md](docs/blockers.md) | Escalation, wake watcher, `nh reply` |
| [adapters.md](docs/adapters.md) | Intake, context, VCS and CI backends |
| [eval.md](docs/eval.md) | Golden set, replay scoring, shadow mode |
| [CHANGELOG.md](CHANGELOG.md) | What changed, per release |
## Development
```bash
uv sync
uv run pytest -q
uv run nh --help
```
Issues and pull requests welcome; run `uv run pytest -q` before submitting.
If no_human saved you a review cycle, a star helps other people find it:
[](https://github.com/no-human-ai/no_human/stargazers)
## License
MIT — see [LICENSE](LICENSE). The licence covers the code, not the name:
[TRADEMARK.md](TRADEMARK.md) is the policy on using "no_human" and the logo.
Packaging a binary carries obligations the source tree does not, listed in
[THIRD-PARTY-NOTICES.md](THIRD-PARTY-NOTICES.md).
What people ask about no_human
What is no-human-ai/no_human?
+
no-human-ai/no_human is subagents for the Claude AI ecosystem. From ticket to reviewed pull request. Free and open-source, on your machine. It has 10 GitHub stars and its last recorded update is dated 2026-08-20.
How do I install no_human?
+
You can install no_human by cloning the repository (https://github.com/no-human-ai/no_human) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.
Is no-human-ai/no_human safe to use?
+
Our security agent has analyzed no-human-ai/no_human and assigned a Trust Score of 87/100 (tier: Trusted). See the full breakdown of passed checks and flags on this page.
Who maintains no-human-ai/no_human?
+
no-human-ai/no_human is maintained by no-human-ai. The last recorded GitHub activity is dated 2026-08-20, with 7 open issues.
Are there alternatives to no_human?
+
Yes. On ClaudeWave you can browse similar subagents at /categories/agents, sorted by popularity or recent activity.
Deploy no_human to your cloud
Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.
Maintain this repo? Add a badge to your README
Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.
[](https://claudewave.com/repo/no-human-ai-no-human)<a href="https://claudewave.com/repo/no-human-ai-no-human"><img src="https://claudewave.com/api/badge/no-human-ai-no-human" alt="Featured on ClaudeWave: no-human-ai/no_human" width="320" height="64" /></a>More Subagents
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
The agent that grows with you
Java 面试 & 后端通用面试指南,覆盖计算机基础、数据库、分布式、高并发、系统设计与 AI 应用开发
Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype to production without rebuilding the stack.
The agent engineering platform.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.