Comments & review
Comment on any selection, review suggested edits, approve a specific version of a document, and request sign-off from a named person.
Commenting
Select any text in Viewing mode and choose Comment. Comments anchor to exactly what you selected — a word, a paragraph, several blocks, or a table region — and the anchored text is highlighted in the document.
The Comments panel (the speech-bubble button in the toolbar) lists everything on the document. Each comment supports:
- Reply — threaded discussion under the comment.
- Resolve — mark it handled, after a confirming tap. Resolved comments leave the document text alone.
- Assign — hand the comment to a teammate or to a connected AI agent as a work item. The picker lists people and agents together, with agents badged as agents so you always know which you are handing work to. Unassign takes it back.
Naming someone in a comment
Type @ anywhere in a comment, a reply, or the note on a suggestion, and DraftMesh offers the people and agents already working in this workspace. Picking one drops their name into your text as ordinary prose — @Ada Chen — so the mention still reads correctly in any other editor, while DraftMesh also records it as a real reference. On a phone, that reference is what puts the comment in that person’s Inbox (see On your phone).
Mentioning someone does not grant them anything, and it sends no email. If they can’t reach the document, share it with them.
Use the View toggle at the top of the panel to switch between List (all comments in a rail) and In-place (each comment beside the text it refers to — needs a wide enough window):

If the text a comment anchored to is later deleted or heavily rewritten, the comment isn’t lost — it moves to an Orphaned comments section so the discussion is preserved.
Reviewing suggestions
Suggestions appear in the same panel with Accept and Reject buttons. Accepting applies the proposed text to the document; rejecting removes the proposal and leaves the document unchanged. Only humans can accept — an AI assistant can propose an edit, but never apply one itself.
Approving a document
The document toolbar carries Approve and Request changes — a lightweight sign-off for “this version is good”:

- The badge is a record, not just a name: who decided, when, any note they left, and — once the version history has loaded — exactly which version they decided on.
- View approved version opens that version read-only, so “what did we actually sign off on?” is one click away.
- If the document changes after an approval, the badge greys out and says content changed since — a stale approval can’t masquerade as a current one.
- Request changes records the opposite signal, visible to everyone on the document.
- Mixed decisions stay side by side. DraftMesh never reduces several people’s sign-offs to one overall verdict.
Asking someone to sign off
Request sign-off, beside Approve, turns “could you look at this?” into a tracked ask rather than a message in another app.
- Tick the people you want from the document’s participants, or type a name into Someone else’s name.
- Add an optional note — what should they look at — and choose Send request.
- Each open request shows beside the sign-off controls — “Ada asked you to sign off”, with the version and note where there are any. A request addressed to you is highlighted.
- When you Approve or Request changes, the requests addressed to you close automatically — the badge beside them is the answer.
A request is about the whole document, so it lives in the toolbar rather than as a comment chip in the margin. On a phone, sign-off requests arrive in the Inbox — see On your phone.
Handing comments to an AI assistant
✦ Form reply (next to the document name, with a count of the open comments) turns the document’s comments into a structured brief for an assistant.
- Scope picks My comments or All open comments.
- The prompt is shown in full and is editable before it goes anywhere. Editing it here changes only the brief — never your comments.
- Copy prompt puts it on the clipboard for any AI chat, which is the point of the feature: the assistant needs no connection to DraftMesh at all.
- Where DraftMesh can reach an agent for you, a Send to agent: row appears under the prompt and hands it over directly. Running DraftMesh on your own machine, that target is Claude Code on this machine; with registered agents you pick which one. The row reports back plainly — Sent to … or Send failed — try again.
If your assistant is connected properly, you may not need this at all: see AI assistants (MCP), where agents read comments, answer questions, and file suggestions themselves.