finds.dev← search

// the find

mcollina/githuman

★ 259 · TypeScript · NOASSERTION · updated Apr 2026

Keep the Human in the Loop of coding

GitHuman is a local web UI (Fastify + React) that lets you review staged git changes before committing, aimed specifically at the AI-pair-programming workflow where an agent writes the diff and a human needs to vet it before it lands. It's for developers running Claude Code, Copilot, or Cursor who want a real diff viewer with inline comments instead of reading raw `git diff` output, plus a CLI handoff (`githuman ask`) so the agent itself can pause and wait for human sign-off.

The `ask` command is the actual interesting idea here: an agent can call `githuman ask`, block, and get structured feedback (comments, todos, approval status) back as JSON once a human clicks through in the browser — that's a real human-in-the-loop primitive, not just a diff viewer with a CLI wrapper. It uses Node's native SQLite and keeps everything local with no network calls, so there's no account, no server dependency, and no data leaving the machine. Test coverage is unusually thorough for a 259-star project — Vitest/node:test unit tests plus a real Playwright e2e suite covering auth, image diffs, markdown rendering, and the staged-changes flow, which suggests the author is actually maintaining it rather than shipping a demo.

Node.js 24+ is a hard requirement, which will quietly break on anyone still on an LTS line (20/22) until they upgrade just to try a CLI tool. Review state lives in a single SQLite file under a gitignored `.githuman/` folder — there's no shared storage or sync, so review history is single-machine and disappears if that machine's disk does, with no export/import path beyond markdown dumps of individual reviews. Auth is opt-in (`--auth` flag or env var) rather than on by default, so `githuman serve --host 0.0.0.0` with default settings exposes an unauthenticated review server with git-diff access on the network. It's effectively a one-maintainer project (Matteo Collina) at this size — fine for now, but worth knowing before building a team workflow around it.

View on GitHub → Homepage ↗

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →