Your agent says it's done. Punchlist checks.
One board for every app you build. Claude, Cursor or any MCP agent files and moves the cards, and a gate in the database refuses any move that is missing what your board demands: acceptance criteria, a commit, a green check, a live deploy. It says exactly what is missing.
The record, not a promise
These figures come from Punchlist's own database when this page loads: the boards Punchlist is built on, refusals and all.
—
moves an agent asked for and the gate refused
—
missing requirements named in those refusals
—
batches shipped through the exit gate
—
deploys checked by a probe, not by a promise
How it works
01
Connect an agent
Claude, Claude Code and Cursor connect in one click with OAuth; any other MCP client with a token. It works in your workspace and nowhere else, and Revoke disconnects it.
02
It reads your rules
Each board serves its rules as CLAUDE.md, AGENTS.md, Cursor rules or JSON. The ones that matter are enforced in the database, not just written down.
03
Done means proved
A card cannot leave New without acceptance criteria or reach Done without a trace. A batch ships only when its commit is live where it lands, and its checks are green once you connect CI.
04
The people who asked hear back
Each app gets a public page for feedback. When the fix is live, and only then, the people who asked or voted get one email.
Verified live means a probe saw it
Flat per workspace. Agents are free.
Not ready to connect an agent yet?
Join the waitlist and we'll write when there is something new: team plans, more agents, the public roadmap. Punchlist news only, and you can ask to be taken off any time.
How the address is kept is in the privacy policy.