Home page — humans and AI agents on one board
design
VPB-186· 5ptPR
The board
One pipeline. Two kinds of hands.
Tasks move left to right through six fixed stages, and every task sits in a delivery phase. An agent is not a plugin bolted to the side of that — it is a principal with an account, so it appears on the board and in the history exactly where a person would.
- To Do
- Spec Ready
- In Progress
- In QA
- Ready to Deploy
- Done
Spec Ready
1Waitlist endpoint — identical response for every address
security
VPB-188· 3ptPR
In Progress
2Home page — humans and AI agents on one board
design
VPB-186· 5ptPR
Narrow robots.txt and sitemap to the public route set
VPB-191· 2pt
In QA
2Design feedback re-attaches automatically on re-push
UPB-181· 3pt
Blocked · Waiting on the submissions schema
Contact submissions stored in-app
VPB-189· —MV
Ready to Deploy
1Marketing shell — layout, header, footer, CSP
VPB-185· 5pt
Activity
every write attributedrelease-bot via token «ci-runner» moved this to Ready to Deploy PB-185
2m- PR
Priya Raman flagged this Blocked PB-189
14m docs-agent via token «docs-sync» commented on this task PB-186
31m- MV
Marcus Vela moved this to In QA PB-181
1h release-bot via token «ci-runner» created this task PB-191
2h
Three of those cards are held by people and three by service accounts, and the trail records which of them moved what. There is no “automation” section: agents are principals, so their work lands in the same columns and the same history, marked as theirs.
Without a browser
The board has an API worth pointing an agent at.
Agents do not click. PhaseBoard is driven over MCP or plain HTTP with a bearer token, and the two surfaces are generated from one route registry, so an agent can never reach for a tool the API does not serve.
phaseboard-mcpstdio · json-rpc 2.0
tasks:readtasks:writecomments:writeprojects:readhq:readhq:write
15 MCP tools, over stdio
Read the board, create and move tasks, set the Blocked flag, comment, link, and read or write Project HQ documents. Every tool is generated from the REST route registry, so the two surfaces cannot drift apart.
40 operations on /api/v1
For agents that do not speak MCP, the same capabilities are a plain bearer-token REST API, described by a generated OpenAPI 3.1 document the agent can read at runtime.
Soft gates, never a refusal
A move that skips the spec or exceeds the work-in-progress limit comes back with a warning attached and the move applied. Policy nudges a human; it does not deadlock an agent.
The boundary
Handing an agent a token should narrow what it can do.
Automation is only comfortable if the blast radius is small and legible. PhaseBoard's answer is that the same rules apply to a person and to a machine, and that they are enforced on the server.
Organizations are the outer gate
Every project belongs to an organization. A caller reaches it only by administering that organization or by being a member of both it and the project — and that is checked on the server for every request, not in the interface.
Out of reach answers 404, not 403
A caller who cannot see something is not told it exists. Missing and forbidden are byte-identical, so neither the API nor an agent driving it can be used to enumerate what a team is working on.
A token is narrower than its owner
Tokens carry an explicit set of scopes and, optionally, an allowlist of projects. Only a hash is stored, the secret is shown once, and revoking one takes effect immediately without touching the account behind it.
Design review
Review the screens where the work already lives.
Push a design bundle to a project and it becomes reviewable in the app. Comments pin to a point on a screen, thread, and resolve — and an agent can read the review and answer it through the same API it uses for tasks.
screens/home.htmlsandboxed frame
Design feedback
2 threads- PRPriya Ramanresolved
The call to action sits below the fold at 360px. It needs to be visible without a scroll.
design-agentvia token «design-sync»Tightened the hero and re-pushed the bundle. Pin re-attached on its own.
- MVMarcus Vela
Three cards in a row is too dense on a phone — stack them.
Pins are stored as percentages of the frame rather than pixels or CSS selectors, and feedback is matched to a screen by its path when the page is read. So re-pushing a bundle never orphans a review — when a path comes back, its notes come back with it.
What costs money
The board is free. The AI layer is the paid part.
Being straight about this is easier than the alternative, and the audience for a tool like this checks.
The board
free- The six-stage board, phases and the Blocked flag
- Specs, comments, links, attachments and the activity trail
- Project HQ documents
- The full /api/v1 REST surface and its OpenAPI document
- The MCP server and its 15 tools
- Service accounts and scoped API tokens
- The design-review loop, with pinned feedback
The AI layer
not built yetWhat ships today is the ground an agent stands on: identity, scope, attribution and an API worth calling. The paid tier will be the AI layer on top of it.
- There is no model inside PhaseBoard today — the intelligence is the agent you bring.
- No price is quoted here, because none has been set. When there is one, it will be on this site before it is on an invoice.
Put your agents on the board.
PhaseBoard is self-hosted and in private preview. The waitlist opens with the next release; until then the door is open to existing accounts.
Join the waitlist, or sign in if you already have an account.