mdcollab.dev Join the waitlist

Review plans the way you review code.

Markdown plans become pull requests. Comment on any line, approve a version, and track the GitHub PRs that build it.

Join the waitlistWatch the demo
How mdcollab.dev works
  1. You start with an idea.
  2. In mdcollab.dev, you brainstorm it with your own agents, like Claude, Codex or an open-weight model, using your existing subscription. No API keys are needed, and everything stays on your machine.
  3. You combine their ideas into one markdown plan, still on your machine.
  4. You push the plan for review. This is the first time it leaves your machine.
  5. In mdcollab.dev, teammates comment on exact lines and approve it.
  6. The plan is approved in mdcollab.dev.
  7. Back on your machine, your local agent implements the approved plan.
  8. Each step opens a pull request in your Git host, linked to the plan.
  9. Pull request status syncs back to mdcollab.dev, where you track what has shipped.

Your agents. Your subscription. No API keys.

mdcollab.dev works with the agents you already use: Claude, Codex and open-weight models, connected through your own subscription. Brainstorming, planning and building all run on your machine. Nothing leaves it until you push a plan for review.

  • Bring your own agentClaude, Codex or any open-weight model you run.
  • No API keys to set upEvery client connects through the subscription you already have.
  • Private until you share itPlans stay local until you push them to reviewers.

See it in action

A short tour of a real plan review. Pause it at any point and click around. Everything in the demo works.

Product tourPress play to watch the tour, or click around to try it yourself.
~1.5 min
Plan

The whole file, as a rendered page or as raw markdown. Comment in either view.

Changes

A line-by-line diff between plan versions. Press + on any line to comment.

Review

Submit comments as a review that approves, comments, or requests changes.

Linked PRs

Every step of the plan, with the GitHub PRs that implement it and their checks.

Conversation

The plan's history: versions, reviews, linked PRs, and the merge.

Everything a plan review needs

Design docs, RFCs, rollout plans and runbooks get the same rigor as the code they describe.

L42 +

Line-level comments

Comment on any line of a .md plan. Batch comments into a review, reply in threads, and resolve them as the author revises.

✓ 2/2

Reviews and approvals

Approve, comment, or request changes. Require approvals from owners like Finance or Security before a plan merges.

v2 → v3

Version diffs

Every push is a new version. See exactly what changed after feedback instead of rereading the whole document.

#1283

Linked PRs

List GitHub PRs in the plan's frontmatter. mdcollab tracks each one per step, with status and checks, so you can see how much has shipped.

How it works

  1. Push a planKeep plans as markdown in your repo, like plans/billing-ledger.md. mdcollab opens a review for each change.
  2. Review togetherEngineers, PMs and stakeholders comment on lines and approve versions.
  3. Merge and trackThe approved plan lands on main. Linked PRs report progress back to the plan until every step ships.

Get early access to mdcollab.dev

We're opening a private beta soon. Join the waitlist and we'll email you when your invite is ready.

  • Free during the beta
  • For solo builders and teams
  • Works with your existing markdown files

All fields are required.

Personal or work email, either is fine.
Just you? Enter "Independent".

No spam. One email when your invite is ready.