Updated June 13, 2026

How anchored comments work on a Drafty canvas

Quick answer

Click any element on a Drafty canvas — a heading, paragraph, image, or table — and your comment pins to that element, Figma-style. The pin stays put even after you push a new version, so feedback never drifts from the thing it's about.

Anchored comments pin feedback to the exact element it's about. Click a heading, paragraph, image, table, list item, or code block on a canvas, and your comment attaches to that element as a threaded pin — the same way you drop a comment on a frame in Figma.

The pin tracks the element, not a spot on the page. So when you push a new version, the comment stays with the thing it was about instead of floating loose.

Click an element to anchor a comment

Open a canvas at its link and click any element you want to talk about. A comment box opens, pinned right there. Type your note and post it.

You don't need an account to do this. Anyone with the link can comment as a named guest. Want to keep your comments under one identity? Sign in with a magic code — a one-time code emailed to you — and your guest comments fold into your account.

Threaded replies

Each pin is a thread, not a single note. Anyone viewing the canvas can reply under a comment, so a back-and-forth stays in one place next to the element it's about.

If you publish a canvas for feedback on an AI-generated document, this is where the conversation happens — every thread tied to the line, image, or section it points at.

Live cursors and presence

When more than one person is on a canvas, you see live cursors and presence — who else is viewing, in real time. It's easier to comment together when you can tell someone's already in there reading the same paragraph.

Resolve and reopen

When a thread is handled, resolve it. Resolved threads tuck out of the way so the canvas stays readable, but they aren't deleted — reopen one any time it needs another pass.

How threads get answered depends on the canvas mode you set. In feedback mode, Claude waits for your go-ahead before acting on comments. In live mode, it works threads as they arrive.

Pins survive new versions

Every push saves a new version of the canvas. A comment stays anchored to its element across those versions, so feedback doesn't reset each time you ship a change.

To act on the feedback, edit your file and push it again:

  1. Make your changes in the source file.
  2. Run drafty canvas push report.html to save a new version.
  3. Open the canvas — the threads are still pinned where you left them.

That's the loop: comment on the exact element, ship a fix, and the conversation carries over.

Create your first canvas

Frequently asked

What can I attach a comment to?
Any element on the canvas — a heading, paragraph, list item, image, table, or code block. Click it and the comment pins there as a thread.
Do comments move if the content changes?
A comment stays anchored to its element across new versions — the pin tracks the element, not a fixed spot on the page, and every push re-anchors each thread on the server, so even a long run of edits can't slowly detach a pin. If an element is removed entirely, its thread isn't lost: it stays in the comments rail, marked as removed.
How do I mark a thread done?
Resolve the thread when the point is handled. Resolved threads tuck away but aren't deleted, so you can reopen one if it needs more work.
Do readers need an account to comment?
No. Anyone with the link can comment as a named guest with no signup. Sign in later with a magic code and your guest comments fold into your account.

Related