Create and share your first Drafty canvas

To create your first canvas, push an HTML or Markdown file with the Drafty CLI. You get back a link at drafty.im/canvas/<slug>, and anyone who opens it can leave comments anchored to the exact element they're looking at — a heading, a paragraph, a table, a code block.

The whole flow is two commands: sign in once, then push the file. Here's each step.

Sign in with drafty login

Run drafty login. It prints a link, you open it in a browser and enter your email, and you're signed in on the CLI. You only do this once per machine.

If you'd rather not run anything, you can ask Claude to "drafty this" file instead — the same plugin does the push for you.

Push a file with drafty canvas push

Point the CLI at the file you want to share:

drafty canvas push report.html

The CLI reads the file and figures out whether it's HTML or Markdown — you don't pass a flag. An HTML file renders as a full standalone page that keeps your own styles; a Markdown file renders as clean, styled prose. When the push finishes, the CLI prints the canvas link.

Set the title with --title

The title shows up on the page and in link previews. Set it with --title:

drafty canvas push report.html --title "Q3 report"

You can change the title later by pushing again with a new --title. Every push saves a new version, so you can always preview and restore an earlier one.

Share the link

Copy the drafty.im/canvas/<slug> link and send it however you like — Slack, email, a message. The link unfurls with its title and a preview image in Slack, X, and Notion, and Notion, Coda, and Medium can embed it as a live, scrollable view.

Because it's a real web page, the link opens in any browser, including a phone. That's the part a raw downloaded .html file can't do.

They open it and comment

Whoever you send it to clicks any element on the canvas and leaves a threaded comment pinned right there, Figma-style. They can comment as a named guest with no signup. You'll see live cursors showing who else is viewing.

By default a canvas is in feedback mode: people comment and nothing changes until you say so. When you push an updated version, each comment stays anchored to its element. To go further and have Claude read the comments and ship a new version, see review Claude Code changes.

Then make it standing

The first canvas is a one-off push. The habit that sticks is letting Claude write to canvases on its own — todos when it needs you, proof when it ships, a summary when a session ends. It's one block in your CLAUDE.md: How do I get Claude to update my canvases on its own?