Skip to content
Back to search

no-human-ai

MarketplaceWorks with Claude CodeGitHub

The no_human plugin for Claude Code: hand a task to your local no_human and check on it without leaving the session.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/no-human-ai--no-human/badge.svg)](/listings/no-human-ai--no-human)

HTML

<a href="/listings/no-human-ai--no-human"><img src="/api/listings/no-human-ai--no-human/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

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](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](https://github.com/astral-sh/uv), git, and Node with npm for the board build.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 36 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "$schema": "https://json.schemastore.org/claude-code-marketplace.json",
  3. "name": "no-human-ai",
  4. "description": "The no_human plugin for Claude Code: hand a task to your local no_human and check on it without leaving the session.",
  5. "owner": {
  6. "name": "eyalgolan",
  7. "url": "https://getnohuman.com"
  8. },
  9. "plugins": [
  10. {
  11. "name": "no-human",
  12. "source": "./plugins/no-human",
  13. "displayName": "no_human",
  14. "description": "File a task with no_human and check on it without leaving Claude Code: task_add and task_status over your local no_human server (127.0.0.1:8420). no_human plans, codes, tests and has the work reviewed by a second model, then opens the pull request and stops. Also ships nh gate: run the fresh-session reviewer and tamper guard over your current branch or a GitHub pull request, no server required.",
  15. "homepage": "https://getnohuman.com",
  16. "repository": "https://github.com/no-human-ai/no_human",
  17. "license": "MIT",
  18. "category": "development",
  19. "keywords": [
  20. "mcp",
  21. "coding-agent",
  22. "pull-request",
  23. "code-review",
  24. "jira",
  25. "linear",
  26. "sdlc",
  27. "review-gate",
  28. "tamper-guard"
  29. ],
  30. "author": {
  31. "name": "eyalgolan",
  32. "url": "https://getnohuman.com"
  33. }
  34. }
  35. ]
  36. }
README.md · README · 443 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <div align="center">
  2. <img src="docs/assets/nh-mark.png" alt="" width="140" height="140">
  3. # no_human
  4. <!-- mcp-name: io.github.no-human-ai/no_human -->
  5. **From ticket to reviewed pull request.**<br>***Free and open-source, on your machine.***
  6. **English** · [简体中文](README.zh-CN.md) · [日本語](README.ja.md) · [한국어](README.ko.md) · [Español](README.es.md) · [Français](README.fr.md) · [Deutsch](README.de.md) · [Português (Brasil)](README.pt-BR.md)
  7. [![latest release](https://img.shields.io/github/v/release/no-human-ai/no_human?label=release&color=4C9AFF)](https://github.com/no-human-ai/no_human/releases/latest) [![CI](https://img.shields.io/github/actions/workflow/status/no-human-ai/no_human/ci.yml?branch=main&label=CI)](https://github.com/no-human-ai/no_human/actions/workflows/ci.yml) [![python 3.12+](https://img.shields.io/badge/python-3.12%2B-blue)](https://www.python.org/) [![license MIT](https://img.shields.io/badge/license-MIT-green)](LICENSE) [![downloads](https://img.shields.io/github/downloads/no-human-ai/no_human/total?label=downloads&color=4C9AFF)](https://github.com/no-human-ai/no_human/releases) [![Discord](https://img.shields.io/badge/Discord-join-5865F2?logo=discord&logoColor=white)](https://discord.gg/mSARvj6yW6)
  8. [getnohuman.com](https://getnohuman.com) · [Quickstart](docs/quickstart.md) · [Docs](docs/README.md) · [Watch it work a sprint](https://getnohuman.com/demo) · [Discord](https://discord.gg/mSARvj6yW6)
  9. [![Download for macOS](https://img.shields.io/badge/Download%20for-macOS-4C9AFF?style=for-the-badge)](https://github.com/no-human-ai/no_human/releases/latest) [![Download for Windows](https://img.shields.io/badge/Download%20for-Windows-4C9AFF?style=for-the-badge)](https://getnohuman.com/) [![Download for Linux](https://img.shields.io/badge/Download%20for-Linux-4C9AFF?style=for-the-badge)](https://getnohuman.com/)
  10. <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>
  11. <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>
  12. </div>
  13. The AI coding factory you <ins>**can trust**</ins>:
  14. - **A plan before any code**, from the ticket plus what it finds in your repo.
  15. When planning fails, the coder is told it is working without one; when the
  16. change is judged trivial the plan is skipped without telling the coder, by
  17. design — the skip is still stated in the run's event stream.
  18. - **An adversarial review.** A different model, in a session that never saw the
  19. coder's transcript, told to refute "done". You get a pass/fail checklist
  20. citing file and line — never a numeric self-score.
  21. - **A tamper guard.** Deleted tests, new skips, an assertion turned into a
  22. tautology — counted mechanically before the review gate runs, then justified
  23. against your acceptance criteria or the attempt stops.
  24. - **Proof the fix fixed the bug.** The tests offered as evidence must fail at
  25. the merge base and pass on the new tree — the reproduction gate runs both.
  26. Out of the box that binds a Python bug fix; `repro_gate.mode: required` binds
  27. every kind and every change.
  28. - **Your tests run**, locally and optionally through your CI — and a PR that
  29. found no test command says **NOT RUN** on its face.
  30. - **An honest stop.** When it cannot finish it stops and says why — a specific
  31. question when your answer would unblock it, a structured record when it has
  32. simply run out of budget — never an invented plausible diff.
  33. **What the gate caught**
  34. no_human builds no_human. Over 65 days on its own board, none of this reached a pull request:
  35. - **505 of 1,709 attempts** the coder called done were sent back by the second model, each with a pass/fail checklist citing file and line.
  36. - **44 attempts** were stopped before the review even ran, for deleting or weakening a test.
  37. - **46 bug-fix proofs** were refused because the test offered as evidence passed on the old code too.
  38. [How these were counted](https://github.com/no-human-ai/no_human/releases/tag/metrics-2026-09)
  39. ## Install
  40. ### One line (CLI + board)
  41. ```bash
  42. uv tool install no-human # or: pipx install no-human — the wheel ships the board
  43. nh init && nh doctor # token, config, first repo; then prove the install is real
  44. ```
  45. ### Desktop app
  46. [![Download for macOS](https://img.shields.io/badge/Download%20for-macOS-4C9AFF?style=for-the-badge)](https://github.com/no-human-ai/no_human/releases/latest) [![Download for Windows](https://img.shields.io/badge/Download%20for-Windows-4C9AFF?style=for-the-badge)](https://getnohuman.com/) [![Download for Linux](https://img.shields.io/badge/Download%20for-Linux-4C9AFF?style=for-the-badge)](https://getnohuman.com/)
  47. Each release ships a SHA-256 alongside the artifact. Platform notes and the
  48. first-run walk-through: [docs/quickstart.md](docs/quickstart.md).
  49. ### From source
  50. ```bash
  51. git clone https://github.com/no-human-ai/no_human.git && cd no_human
  52. uv sync # installs the `nh` entry point into .venv
  53. (cd web && npm install && npm run build) # builds the board (cold first install can take minutes)
  54. uv run nh init # token, config, first repo (about 2 minutes)
  55. uv run nh doctor # verify the install is real before relying on it
  56. ```
  57. The `web` build is not optional if you want the board: a source checkout ships
  58. no `web/dist`, so without it `nh start` serves the API only and renders no UI.
  59. Needs Python 3.12+, [uv](https://github.com/astral-sh/uv), git, and Node with
  60. npm for the board build.
  61. ## Product highlights
  62. <table>
  63. <tr>
  64. <td width="36%" valign="middle">
  65. <h3>A plan before any code</h3>
  66. <p>Acceptance criteria you can check, written from the ticket and your repo.</p>
  67. </td>
  68. <td width="64%">
  69. <img src="docs/assets/readme/highlight-plan.png" alt="The task's plan: what we understood as three acceptance criteria, the two files to change, the approach, the test plan, what is out of scope, and the verification command." width="100%" />
  70. </td>
  71. </tr>
  72. <tr>
  73. <td width="36%" valign="middle">
  74. <h3>An independent reviewer</h3>
  75. <p>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.</p>
  76. </td>
  77. <td width="64%">
  78. <img src="docs/assets/readme/highlight-verdict.png" alt="The reviewer's verdict: PASSED, each acceptance criterion ticked with the file and line that satisfies it, one non-blocking nit with the diff it points at." width="100%" />
  79. </td>
  80. </tr>
  81. <tr>
  82. <td width="36%" valign="middle">
  83. <h3>Your tests, on the PR's face</h3>
  84. <p>Run locally or through your CI. No test command found reads <b>NOT RUN</b>, never blank.</p>
  85. </td>
  86. <td width="64%">
  87. <img src="docs/assets/readme/highlight-tests.png" alt="The task's Test results panel: CLEAN, 5 passed of 5 total, with the pytest output underneath." width="100%" />
  88. </td>
  89. </tr>
  90. <tr>
  91. <td width="36%" valign="middle">
  92. <h3>A tamper guard</h3>
  93. <p>Deleted tests, new skips and tautological assertions are counted before review. Unjustified, the attempt stops.</p>
  94. </td>
  95. <td width="64%">
  96. <img src="docs/assets/readme/highlight-tamper.png" alt="A stopped attempt: a red TAMPER DETECTED banner, the reviewer verdict FAILED, and the blocking finding that three tests were deleted without an acceptance criterion to justify it." width="100%" />
  97. </td>
  98. </tr>
  99. <tr>
  100. <td width="36%" valign="middle">
  101. <h3>Proof the fix fixed the bug</h3>
  102. <p>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.</p>
  103. </td>
  104. <td width="64%">
  105. <img src="docs/assets/readme/highlight-repro.png" alt="The task's event log: tests pass, status reviewing, the reviewer's tamper check reading none, the reproduction gate reading pass, required, then lint, commit and the pull request opening." width="100%" />
  106. </td>
  107. </tr>
  108. <tr>
  109. <td width="36%" valign="middle">
  110. <h3>An honest stop</h3>
  111. <p>When it needs you, it parks with one specific question instead of guessing.</p>
  112. </td>
  113. <td width="64%">
  114. <img src="docs/assets/readme/highlight-question.png" alt="The board's Needs answer lane: one task parked with its question, 'Dedupe by user, or by digest id?', and an Answer question button; the Working and Review PR lanes beside it." width="100%" />
  115. </td>
  116. </tr>
  117. <tr>
  118. <td width="36%" valign="middle">
  119. <h3>Your tracker's tickets, on your board</h3>
  120. <p>Pick Jira or Linear tickets from the backlog (monday.com boards are polled). Each one is scoped with you before it starts.</p>
  121. </td>
  122. <td width="64%">
  123. <img src="docs/assets/readme/highlight-backlog.png" alt="The Backlog synced from Jira: four matching tickets selected, and a Start 4 tasks button." width="100%" />
  124. </td>
  125. </tr>
  126. </table>
  127. <sub>Stills: the real board on a demo workload.</sub>
  128. ## Run one task
  129. Run `nh` with no arguments for the shell: your lanes, a live event tail, and an
  130. intake you describe a task to in plain English. Every command below still works.
  131. ```bash
  132. nh # the shell
  133. nh start # board + worker on 127.0.0.1:8420
  134. nh task add https://github.com/org/repo/issues/42 --repo ~/git/repo
  135. nh status # needs-you / working / waiting / done
  136. nh review <id> # the reviewer's evidence checklist
  137. nh diff <id> # the diff it wants to ship
  138. nh approve <id> # your approval squash-lands the PR (git.approve_identity)
  139. nh reject <id> --reason "..." # send it back with feedback
  140. ```
  141. ## Integrations
  142. Point no_human at the tracker you already use and it pulls the tickets to your
  143. board — a tracker's filter lives in your config, never in a task's own text,
  144. and a transport error logs and retries on the next tick instead of crashing
  145. the pool.
  146. | Tracker | How tickets arrive | Filter you configure |
  147. |---|---|---|
  148. | **Jira Cloud** | Polled via REST `search/jql` (HTTP Basic `email:token`) | `integrations.jira.jql` |
  149. | **Linear** | Polled via the GraphQL API | `integrations.linear.team_key` + `state_types` + `label` |
  150. | **monday.com** | Polled via GraphQL v2 | `integrations.monday.board_id` + `status_column` + `todo_labels` |
  151. With write-back on (`write_back`, off by default), the ticket moves with the
  152. task — matched by status category, type, or the label you name, never a
  153. hard-coded transition id — and gets the PR link; a task that needs a human is commented on, never
  154. transitioned. GitHub and
  155. GitLab issues import as tasks by URL, and PRs or MRs open on your own host;
  156. Slack and Teams get a message when a task needs you; Jenkins and CircleCI can
  157. run your test layers and gate the loop. Setup for each:
  158. [docs/adapters.md](docs/adapters.md).
  159. **Watch the Jira flow end to end** — tickets synced from a Jira board, scoped,
  160. implemented, and delivered as a review-passed pull request (click for the full
  161. video with every step):
  162. [![Jira flow demo](https://getnohuman.com/assets/demo-jira.gif)](https://getnohuman.com/assets/demo-jira.mp4)
  163. <p align="center">▶️&nbsp;&nbsp;<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>
  164. ## GitHub Action
  165. Run the same adversarial reviewer and tamper guard as a pull-request check —
  166. one shot, no daemon, no `~/.no_human` database, and not the queueing `nh
  167. review` CLI path. It judges the diff alone: unlike a local run, it collects no
  168. lint, wiring or type evidence and does not explore the repository. It posts a single pass/fail checklist comment with
  169. `file:line` citations, found by its own marker and updated in place on every
  170. run rather than creating a new one each time. That comment `@`-mentions the
  171. pull request's author (from the event payload, never the diff or the PR's
  172. own title/body) — GitHub notifies on the first run, which creates the
  173. comment, but not on later runs, which edit it in place, and the comment says
  174. plainly which case a given run was.
  175. ```yaml
  176. # .github/workflows/review-gate.yml
  177. name: no_human review gate
  178. on:
  179. pull_request:
  180. permissions:
  181. contents: read
  182. pull-requests: write
  183. jobs:
  184. review:
  185. runs-on: ubuntu-latest
  186. steps:
  187. - uses: actions/checkout@v4
  188. with:
  189. fetch-depth: 0
  190. ref: ${{ github.event.pull_request.head.sha }}
  191. - uses: no-human-ai/no_human@v0.2.4 # a release tag; a reviewed SHA is stronger — see below
  192. with:
  193. credential: ${{ secrets.ANTHROPIC_API_KEY }}
  194. github_token: ${{ github.token }}
  195. ```
  196. `permissions.contents: read` lets `actions/checkout` read this repository;
  197. `pull-requests: write` is what lets the Action post/update its own comment.
  198. Neither grants anything broader. The checkout step's explicit
  199. `ref: ${{ github.event.pull_request.head.sha }}` matters too: on a
  200. `pull_request` event, `actions/checkout` otherwise checks out an ephemeral
  201. merge commit rather than the PR's actual head, and the Action reviews and
  202. cites line numbers against whatever tree is on disk — it refuses to run
  203. rather than review the wrong one, so omitting `ref:` here turns into a red,
  204. actionable exit `2`, not a silent misreview.
  205. There is no `v1` tag for this Action yet. `v0.2.4` was the first release tag to
  206. carry `action.yml`, so `no-human-ai/no_human@v0.2.4` resolves and is what the
  207. example above pins — but a release tag is not a moving major version, and
  208. `@main` is whatever landed most recently. **A commit SHA you have reviewed
  209. (`no-human-ai/no_human@<sha>`) is stronger still**: a branch moves by
  210. definition and a tag can be moved, so a SHA is the only form under which a
  211. later change to this repository cannot alter what your workflow runs — and this
  212. Action runs with your credential.
  213. `credential` takes either shape of your own Anthropic credential — an
  214. `ANTHROPIC_API_KEY` (`sk-ant-api...`) or a Claude subscription OAuth token
  215. minted with `claude setup-token` (`sk-ant-oat...`) — auto-detected from its
  216. prefix, or pinned explicitly with `credential_mode: oauth` /
  217. `credential_mode: api_key`. Whichever shape you pass, the other credential
  218. path is scrubbed from the job's environment before the reviewer runs, and the
  219. value itself is masked in the log the moment it is read.
  220. **A credential is required, and there is no silent fallback.** If
  221. `secrets.ANTHROPIC_API_KEY` (or whatever secret you wire into `credential`)
  222. is empty, unset, or a shape the Action can't recognize even in `auto` mode,
  223. the run fails loudly at exit code `2` — naming the `credential` input and
  224. the secret it expects — before the reviewer, or any GitHub API call, ever
  225. runs. The same fail-closed rule applies if the reviewer itself errors out or
  226. the model call is rejected: those runs exit `2` too. The Action never posts
  227. a PASS, and never exits `0`, for a credential or reviewer failure — but a
  228. green check does **not** always mean the gate reviewed code: a fork pull
  229. request skips with exit `0` and no reviewer call (see below), and a pull
  230. request with an empty diff (nothing to review) posts a synthetic PASS with
  231. no reviewer or tamper-guard call. If you make this a required check, treat
  232. both of those as "did not review," not as an approval. A diff larger than the
  233. reviewer's single-turn cap is refused with exit `2` instead of being reviewed
  234. as a truncated prefix, so that case is never a green check: lower `max_files`
  235. or split the pull request.
  236. **Forks are skipped, not reviewed.** A pull request whose head is not this
  237. repository — including one from an already-deleted fork — never reaches the
  238. reviewer or the model; the Action exits 0 with a comment-free explanation
  239. instead of running review code against an unvetted head in a job that can see
  240. your secrets. `pull_request_target` is refused outright (exit 2), even with a
  241. valid credential, because that trigger is the one shape that can carry a
  242. fork's head into a secret-bearing job.
  243. `workflow_run` is also a supported trigger, reconstructing the pull request's
  244. number, head commit, and changed files over the GitHub REST API instead of
  245. from a `pull_request` payload; because that mode has no checked-out repository
  246. tree, the tamper guard does not run, and the posted comment says so explicitly
  247. rather than implying a clean tamper check.
  248. **Dependabot pull requests fail closed with exit `2`, and that is GitHub's
  249. restriction, not this Action's.** A Dependabot-opened pull request has the
  250. same repository as its head — it is not a fork, so the check above does not
  251. skip it — but GitHub itself withholds repository secrets (and downgrades
  252. `GITHUB_TOKEN` to read-only) from workflow runs it triggers on the
  253. `pull_request` event, as a platform-level guard against a lockfile update
  254. carrying a malicious install script into a secret-bearing job. `credential`
  255. therefore arrives empty on those runs, and this Action's own fail-closed rule
  256. (above) makes that a red, actionable exit `2` naming the missing secret, not
  257. a silent skip or a false PASS. If you require this check and want Dependabot
  258. PRs to go green, either exempt them in your branch protection rules or accept
  259. that they need a maintainer's manual re-run/approval like any other check
  260. that needs a secret GitHub won't hand to a bot-triggered job.
  261. **Cost is bounded by files, not tokens or time.** `max_files` (default `15`)
  262. caps how many changed files are sent to the reviewer, sorted by path,
  263. first-N; the comment reports how many of the total were actually reviewed.
  264. The reviewer runs `single_turn`, so a passing run is one model call over the
  265. capped diff, and a failing one may add a single bounded refute pass — in rough terms, a few cents to a few tens of cents of your
  266. own Anthropic usage depending on diff size, similar in shape to one local `nh
  267. review`. That is separate from the one-time cost of the runner building the
  268. Docker image itself (a few tens of seconds, GitHub-hosted-runner compute,
  269. not model spend) on each run unless your workflow caches the image. Lower
  270. `max_files` (or split large pull requests) to spend less.
  271. The Action never merges, pushes, approves, or edits anything about the pull
  272. request beyond its own single comment — enforced in code, not just by
  273. convention: every GitHub API call is checked against a two-endpoint allowlist
  274. (list/create/update that one comment thread) before it is sent. Set
  275. `fail_on_findings: false` to keep the comment without failing the check, or
  276. `dry_run: true` to print the verdict to the job log/summary and make no
  277. GitHub API calls at all.
  278. **Known limitation: the tamper guard's "full test tree" claim holds for
  279. ASCII test filenames, not non-ASCII ones.** The tamper check walks every test
  280. file in the repository (not just the `max_files`-capped subset sent to the
  281. reviewer) via an unquoted `git ls-tree`, so a test file whose name contains
  282. non-ASCII bytes is listed in git's C-quoted string form (e.g.
  283. `"r\303\251gression_test.py"`) instead of its real path, and silently drops
  284. out of the guard's before/after comparison — deleting or weakening such a
  285. file will not currently be caught. This Action's own diffed/reviewed file
  286. list is not affected by the equivalent problem (it explicitly re-quotes and
  287. re-verifies every path it hands to the reviewer), but the underlying
  288. tamper-check module is out of scope for this Action to change. If your test
  289. suite has non-ASCII test filenames, treat the tamper guard as best-effort for
  290. those specific files until that's fixed upstream.
  291. **Known limitation: two runs racing each other, or a pull request already
  292. carrying 1,000+ other comments, can produce a duplicate.** The Action finds
  293. its own prior comment by listing the PR's comments (up to 10 pages of 100)
  294. and picking the lowest-id one carrying its marker; two runs started close
  295. together can both list before either creates, and each will create its own
  296. comment. A later run of either still converges — it lists again, finds the
  297. lowest-id marked comment, and updates that one — but the extra comment is
  298. not deleted. The same "list, then act" gap means a marked comment that would
  299. only appear on page 11 or later (over 1,000 other comments already on the
  300. pull request) reads as absent and gets a new one created rather than
  301. updated. Both are accepted, documented bounds rather than silent failures:
  302. if your workflow can trigger two runs for the same commit, add a
  303. `concurrency:` group keyed on the pull request to serialize them.
  304. ## MCP server — hand it work from the agent you are already in
  305. no_human ships an **MCP (Model Context Protocol) server**: a stdio bridge, built
  306. on the official Python MCP SDK, that lets Claude Code, Cursor or any MCP client
  307. file work with your local no_human and check on it.
  308. ```bash
  309. nh mcp-serve # the MCP server, over stdio
  310. ```
  311. Two tools, and no more:
  312. | Tool | What it does |
  313. |---|---|
  314. | `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. |
  315. | `task_status(task_id_or_external_id)` | Returns that task's current state — status, attempts, the PR link once there is one. |
  316. It talks to your own no_human at `http://127.0.0.1:8420` and nothing else: no
  317. auth, because that address is localhost, and no service of ours in between. For
  318. Claude Code, the same server ships as a plugin — this repository is its own
  319. plugin marketplace, so the two tools appear in your session after:
  320. ```
  321. /plugin marketplace add no-human-ai/no_human
  322. /plugin install no-human@no-human-ai
  323. ```
  324. Any other MCP client takes the usual stdio entry:
  325. ```jsonc
  326. // .mcp.json
  327. { "mcpServers": { "no_human": { "command": "nh", "args": ["mcp-serve"] } } }
  328. ```
  329. The plugin also ships the `review-this-branch` skill, which does not
  330. need the MCP server or `~/.no_human` at all: it runs `nh gate`, a one-shot
  331. CLI verb that puts the fresh-session adversarial reviewer and the tamper
  332. guard directly on your current branch or a GitHub pull request, using your
  333. own Claude credential, and exits with a pass/fail Markdown checklist,
  334. with nothing installed or running beyond the `nh` CLI itself.
  335. ```bash
  336. nh gate # current branch vs. its merge base with origin's default branch
  337. nh gate --pr <github-pr-url> # a GitHub pull request's head vs. its merge base
  338. ```
  339. ## Docs
  340. | | |
  341. |---|---|
  342. | [quickstart.md](docs/quickstart.md) | Zero to first task, per platform |
  343. | [configuration.md](docs/configuration.md) | Every setting and default |
  344. | [verification.md](docs/verification.md) | The gates, the bounded loop, the limits |
  345. | [security.md](docs/security.md) | Auth boundary, the never-merge rule, guards |
  346. | [blockers.md](docs/blockers.md) | Escalation, wake watcher, `nh reply` |
  347. | [adapters.md](docs/adapters.md) | Intake, context, VCS and CI backends |
  348. | [eval.md](docs/eval.md) | Golden set, replay scoring, shadow mode |
  349. | [CHANGELOG.md](CHANGELOG.md) | What changed, per release |
  350. ## Development
  351. ```bash
  352. uv sync
  353. uv run pytest -q
  354. uv run nh --help
  355. ```
  356. Issues and pull requests welcome; run `uv run pytest -q` before submitting.
  357. If no_human saved you a review cycle, a star helps other people find it:
  358. [![GitHub stars](https://img.shields.io/github/stars/no-human-ai/no_human?style=social)](https://github.com/no-human-ai/no_human/stargazers)
  359. ## Community
  360. Questions, bug reports and runs worth showing: join the [Discord](https://discord.gg/mSARvj6yW6),
  361. post on [r/no_human](https://www.reddit.com/r/no_human/), or open a
  362. [GitHub issue](https://github.com/no-human-ai/no_human/issues).
  363. ## License
  364. MIT — see [LICENSE](LICENSE). The licence covers the code, not the name:
  365. [TRADEMARK.md](TRADEMARK.md) is the policy on using "no_human" and the logo.
  366. Packaging a binary carries obligations the source tree does not, listed in
  367. [THIRD-PARTY-NOTICES.md](THIRD-PARTY-NOTICES.md).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.