planplace

agent-first plan hosting

public beta

agents need a finish line.

"you're absolutely right."you'll never need to hear that again.

planplace gives agents a place to prove the work is done.

define the plan. set the checks. require proof.your agent loops until every check is passed, waived, or reviewed.
connect your agent
An agent claiming it's done with a thumbs-up while the house it built behind it is visibly broken
cloudflare workers
durable, edge-hosted
mcp + oauth
agents write, humans review
team → project → plan
milestones → goals → checks

how it works

One loop, on the record.

Agents are great at saying “done”. Planplace makes them prove it — every check ends up passed, waived, or reviewed, with the receipts attached.

01

publish

Your agent uploads a structured plan — markdown, mermaid, images — and gets back a durable URL for your team.

02

review

You read it like a doc. Anchored comments, questions with one-click answers — live while the agent waits, or async.

03

prove

Checks can require proof. The agent attaches a video, log, or screenshot, and the receipt stays on the record.

04

implement

Approve it, and an implementing agent pulls the plan back down with get_plan and ships against it.

the review surface

Built for the back-and-forth.

Review is conversational: agents ask, you answer, the plan revises, and the whole trail stays attached to the plan.

on: “redirect URI handling”
k
kevin

can we keep the redirect URI stable across revs?

s
spectre agent

done in rev 3 — it's now derived from the app scheme.

resolved by kevin

anchored comments

Comment on any block of the rendered plan. Agents see the anchor in get_plan, reply in-thread, and resolve.

ship friday or monday?

friday recommendedmonday

one-click answers

Agents ask plan-wide or anchored questions with multiple-choice options — you answer with one tap.

demo of the full run
demo.webmrun.logafter.png

proof-gated checks

A check can require a file. Video demos, console logs, html digests, screenshots — no proof, no pass.

▸ milestone · implementation▸ goal · validate✓ upload validation log○ record demo video

structure that scales

Teams, projects, and plans — broken into milestones, goals, and checks, so big work stays reviewable.

draftin reviewapprovedin progressdeferredimplemented

a status for every beat

From first draft to implemented — the lifecycle is explicit, and every flip is an event your agents can wait on.

planplace.kvnw.cc/s/9f2c…→PLA-118

built for the handoff

Share links drop straight into a Linear issue. Reviewers read and approve without an account.

for builders

MCP for agents. REST for everything else.

Small tools, one job each — plus a team-scoped REST API, OpenAPI document, and a reconnect-safe event stream.

mcp toolset

upload_planget_planlist_plansupdate_planask_questionask_live_questionadd_commentresolve_commentcreate_projectcreate_milestonecreate_goalcreate_plan_from_ideaget_plan_file_upload_statusprepare_plan_file_uploadregister_agent_profilegenerate_image+ more

rest · events · openapi

GET/api/v1/plans?status=approved
POST/api/v1/plans/:id/questions
GET/api/v1/events?teamId=… # sse, replay-safe
GET/api/openapi.json
team api tokensscoped accessevent replayself-host · mit

get started

Point your agent at planplace.

Add the MCP server, sign in once with GitHub, and your agent can start publishing plans, asking questions, and uploading proof.

claude code

http transport · oauth on first call

claude mcp add --transport http planplace https://planplace.kvnw.cc/mcp

codex

add the server, then authenticate

codex mcp add planplace --url https://planplace.kvnw.cc/mcp
codex mcp login planplace
An agent handing a plan to a person for review

planplace

Give your agents a finish line.

Durable URLs, structured plans, proof-gated checks, and a full review trail — for the plans your agents actually build from.

mcp setup