Contents

Features

Comments

•4 min read
Comments

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 handed to an AI agent in one click — 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.

A commented passage with an anchor highlight in the document and a margin note open on the right

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 a Comment to AI

This is what makes comments more than review markup.

Write @claude, @codex, or @opencode inside a comment, and a Send to AI button appears on the note. Click it, and Ritemark hands the commented passage plus your note to the AI sidebar, routed to the agent you mentioned. 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.

No copy-paste. No re-explaining the context. The agent receives the exact span you commented on and the note you wrote about it, in one step.

For example, highlight a paragraph that reads awkwardly, add a comment @claude tighten this and cut the repetition, and click Send to AI. Claude Code gets the paragraph and your instruction together, and works on exactly that passage.

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
Send a comment to AI Write @claude, @codex, or @opencode in the comment, click Send to AI
Where comments are stored Inside the Markdown file — they persist across saves
Back to support