
Comments
Mark up a document the way you would on paper, then send the exact passage and your note straight to an AI agent.
As of v1.8.3, Ritemark has comments. Select a passage, add a note, and it shows up as a margin annotation next to your text. The commented span gets an anchor highlight, so you always see what a note refers to. Comments are saved inside the Markdown file itself, so they survive every save and travel with the document.
The reason comments exist here isn't just review markup. A comment can be assigned to an AI agent, and the commented passage plus your note go to the AI sidebar together, so you never have to copy-paste the text or re-explain the context.
New in v1.8.6: comments are a command center for agents. The toolbar badge shows the document's real comment count, a mention is picked up anywhere in the note, and sending runs one ordered task per agent with live status dots in the margin. See Send Comments to AI.

Add a Comment
There are two ways to leave a note.
On selected text. Select the passage you want to comment on, then click Comment in the toolbar. The selected span gets an anchor highlight, and a margin note opens on the right where you type your comment.
A standalone note with ///. Type /// anywhere in the document to drop a quick standalone note without selecting anything first. Use this when the note is about the spot rather than a specific span of text — a reminder, a question, a to-do for later.
Either way, the note lives in the margin rail on the right, lined up with the point in the document it refers to.
Edit an Existing Comment
To change a comment you already left, click its bubble in the margin rail and edit the text in place. There's no separate edit mode to enter — you click the note and start typing.
Send Comments to AI
This is what makes comments more than review markup.
Mention @claude, @codex, or @opencode in a comment and that comment becomes a task for the agent you named. As of v1.8.6 the mention is picked up anywhere in the note, not only at the start, so "this opening reads abrupt, @claude soften it" works exactly like a note that opens with the mention. The mention shows up as an inline chip in the comment, so you can see at a glance which agent a note is aimed at.
The Comments Popover
Open the comments popover from the comment button in the document toolbar. The badge on that button carries the document's real comment count, and the popover header breaks the count down: 4 total · 2 assigned · 2 unassigned.
Assigned comments are grouped by agent, one row per agent with the note text underneath, so you can see what Claude is about to get and what Codex is about to get before anything runs. Comments with no mention stay out of the groups, under a plain line that says Unassigned comments are never sent. A note you left for yourself stays a note.

The Confirm Step
Click Send assigned comments to AI and nothing runs yet. A confirm step appears with a checkbox per agent group and a plain sentence describing exactly what is about to happen: Starts 2 tasks (2 comments) — one per agent, in document order. Uncheck a group to leave it out of this run, then click Start 2 tasks.

Each agent receives a single ordered task built from its own comments, in the order those comments appear in the document. The tasks go into the prompt queue in the AI sidebar, so they run one after another instead of all at once, and you can see them lined up while the current one works.
Live Status in the Margin
Once a run starts, a status dot appears on each margin comment that was sent. The dot tracks that comment's task, so you can keep reading the document and see which notes have already been handled and which are still waiting. When a task finishes, the agent's reply in the sidebar explains what it changed and the dot on the matching comment turns green.

For example, highlight a paragraph that reads awkwardly, add a comment @claude tighten this and cut the repetition, and send it. Claude Code gets the paragraph and your instruction together, and works on exactly that passage. No copy-paste. No re-explaining the context.
Comments Are Saved in the Markdown
Comments persist because they're written into the Markdown file itself, not stored in a separate database. A commented span round-trips as a <mark data-comment> element, and standalone notes are stored as HTML comments in the file.
That means your comments survive every save, come back exactly as you left them when you reopen the document, and travel with the file if you commit it or move it. Because they're part of the file, comment changes show up in git diff like any other edit, so you can review or revert them the same way you would any change to the document.
Known Limitations
Two rough edges in v1.8.3, both fixed in the v1.8.3-ext.1 extension update:
- Multi-bullet comments split per bullet (#150). If you select across several bullet points and comment on them together, the comment currently splits into a separate note per bullet instead of staying as one.
- Comment button low-contrast hover (#151). The Comment button's hover state is hard to see against the toolbar. It still works; it's just faint.
Both are addressed in the v1.8.3-ext.1 extension update, so keeping your extensions current clears them.
Quick Reference
| Action | How |
|---|---|
| Comment on a passage | Select text, click Comment in the toolbar |
| Quick standalone note | Type /// anywhere in the document |
| Edit a comment | Click its bubble in the margin rail and type |
| Assign a comment to an agent | Write @claude, @codex, or @opencode anywhere in the note (v1.8.6) |
| See how many comments a document has | The badge on the toolbar comment button (v1.8.6) |
| Send assigned comments to AI | Open the comments popover, click Send assigned comments to AI, confirm the task count |
| Keep a note private to yourself | Leave the mention out — unassigned comments are never sent |
| Track a running comment task | Status dot on the margin comment (v1.8.6) |
| Where comments are stored | Inside the Markdown file — they persist across saves |
Related
- AI Sidebar - Four agents in one sidebar; where comment tasks queue and run
- Core Editor - Editor features and slash commands
- Agent Library - Browse all agents in one place