I maintain no_human. It's open source, and this month I'm getting it ready for outside contributors, so this post is part announcement, part ask.
What it does: no_human proves the code it wrote is correct. You drop a ticket on the board (or point it at Jira or Linear) and it plans, writes the code, and opens a pull request. Before that PR reaches you, the work is checked by a second model that never saw the coder's session and is told to assume the job is not done. You get a pass/fail checklist that cites files and lines, not a score. If the agent deleted or weakened a test, a tamper guard stops the attempt. For bug fixes, the tests offered as proof have to fail on the old code and pass on the new. It's free and open-source, on your machine.
If you're thinking about contributing, here's what you'd be walking into.
You don't need a Claude account to work on it. The test suite is hermetic: uv sync --frozen && uv run pytest -q -n 4 runs all ~2,980 tests without ever calling a model. A credential only comes into play if you want to run the product end to end.
The good first issues are scoped down to file and line, each with a repro and the command that verifies the fix.
Past those, the one I most want help with is backend adapters. The implementer runs behind a narrow protocol, and I want adapters for more coding agents: opencode, Aider, Goose, Crush, Amp, Qwen Code, and a longer list in the issue. One agent per PR, and comment before you build. Some of these tools have no headless mode, and I'd rather tell you that before you spend a weekend finding out.
Not everything needs Python, either. There are open invitations for UX polish on the web board — frontend and design contributions, with the rule that a sketch or screenshot comes before code — and for making the PRs the agent opens read better: the PR body is the artifact a human judges, and right now it's information-dense but plain.
Fair warning about scope: only the coder seat is swappable. The reviewer, planner and supervisor stay on Claude in every configuration, because the review gate is only worth something if the reviewer is independent of whatever wrote the code. Issue #17 goes into the reasoning.
On process: comment on an issue to claim it, no assignment needed. I reply within 24 hours, review new contributors' PRs within 48, and a claim with no movement for two weeks goes back up for grabs.
Top comments (0)