Board PlannerPeople
A Kanban board, a dense list view, task detail, comments, sprints and a dashboard. Light or dark, desktop or phone.
Self-hosted project board
Hand your boardto an agent.Keep the gate.
People, the REST API and MCP agents work the same tasks through the same permissions. A worker can carry a task from approved to merged on its own — and still stops dead at the checks you configured.
- worktreecp-worktrees/w-3f21
- coding agent14 min · 2 files, 128 lines
- diff-sizepass128 lines / 2 files
- protected-pathspass
- test-presencepassevents.test.ts
- buildpass41s
- test-runpass212 passed
- reviewreject“the cursor is not opaque — it leaks the row id”
branch pushed · comment posted · task moved to Needs human review
You name the columns. Automation reads the role.
Call a column Ready for dev or Shipping — nothing downstream breaks, because every column carries one of six roles and that is what agents key on.
backlogCaptured, not approved. Agents leave these alone.approvedReady to pick up. Workers claim from here.activeBeing worked on right now.reviewA human gate. Automation stops here.blockedHeld up by something outside the task.doneFinished.
Three doors into one model
Not a board with a bot bolted on. The same tasks, the same status rules and the same permission checks behind every entrance.
Agents
An MCP server with twelve tools, so a coding agent reads the backlog and moves tasks straight from your terminal.
Automation
A REST API with project-scoped tokens, webhooks, and workers that pick up approved tasks and run them end to end.
What stops a bad change
The run at the top of this page ends in a rejection because that is the interesting case. Here is what the worker guarantees when it does.
Nothing merges unreviewed
The review gate is a second agent with no memory of writing the code. It sees the diff and nothing else.
Nothing runs before the diff is read
Protected paths are checked before the build gate executes anything, and installs run with lifecycle scripts disabled.
No subprocess inherits your secrets
The child environment is an allowlist. The API token reaches neither the agent nor any dependency’s install script.
Nothing can hide from the gates
The worktree is checked for uncommitted files first, so an agent cannot dodge review by never staging a change.
A rejected branch is never lost
It is pushed before the worktree is discarded, and the task says which gate said no.
A failing task ends up in front of you
Crashes spend an attempt; usage limits refund it. Either way a repeating failure stops cycling and waits for a person.
The rest of it
The board
Columns you define, with roles automation reads. Drag, filter, and see dependencies on the card.
The list
Same tasks as a table. Status and assignee are editable in the row.
The task
Description, acceptance criteria, linked pull requests, dependencies, comments and full history.
The numbers
Velocity, created against completed, and which column the work is piling up in.
Every screen above is in the documentation.
Twenty-seven pages: what each feature does, how to use it, how to install it, and what to check when something looks broken.
Start reading