Review Claude's plan like a PR — point at the line that's wrong.
Push the plan to a canvas. Read it on any screen, comment on the exact step, and Claude revises — version history shows how the plan converged.
You're not alone
“Agentic coding didn't make me faster, it just moved the work to review… No one can review code this fast.”
“The diff view for plan versions is the killer feature here. Watching how the plan shifts between iterations exposes whether Claude is converging or just rephrasing.”
“If you use planning mode a lot like I do and spend way too much time scrolling through and reviewing plans, you've probably felt the same pain.”
Why does reviewing agent output hurt?
Review became the bottleneck
The agent writes faster than anyone can read. A 600-line plausible diff isn't a speedup if you're the one who has to find the 80 lines that matter.
Plans live in a terminal
Plan mode means scrolling a wall of text in a TTY. There's no margin to write in, no line to point at, no way to read it from the couch.
Feedback evaporates in chat
You describe the problem in the prompt, the plan regenerates, and there's no record of what you flagged or whether it stuck.
How Drafty fixes it
The plan becomes a page
One command — drafty canvas push plan.md — and the plan is a readable page on any screen, phone included.
Comment on the exact step
Click the step that's wrong and pin a note to it. Your review is anchored to the line, not floating in chat history.
Claude works the comments
drafty comments inbox hands Claude your notes in the terminal. It revises and pushes the new plan to the same link.
Versions show convergence
Every revision is kept. Flip between v1 and v4 to see whether the plan is actually converging — or just rephrasing.
Read more
See it on a real one
Open one on your phone — it just renders. Then click any line and leave a note — Claude's watching.