Web App
Review comments

Review comments

Use review comments when you want feedback to stay attached to the document while you draft, revise, and export clean deliverables.

Review state is document-owned. Comments, suggestions, highlights, replies, statuses, and assignments are saved with the article package so they can survive local-first editing and package-based sync.

Add a review item

  1. Open a document in the web app editor.
  2. Select the text you want to review.
  3. Choose Comment, Suggest, or Highlight from the selection popover.
  4. Submit the item. It appears in the Review rail and stays anchored to the selected text.

Use each item type for a different review job:

  • Comment starts a discussion on selected text. You can reply, assign, resolve, copy a link, or delete the thread.
  • Suggest proposes replacement text. Reviewers can accept or reject the suggestion from the Review rail.
  • Highlight marks selected text for attention. A note is optional, and highlights can be resolved when they are no longer needed.

Suggestions currently work on selected inline text. If you need to rewrite a larger section, select a smaller phrase or leave a comment with the requested edit.

Work from the Review rail

Open the Review rail to scan, filter, and act on review items in the current file.

The filter menu means:

  • Open shows unresolved comments and highlights, plus undecided suggestions.
  • Mine shows open items created by you or assigned to you.
  • Comments shows open comments and highlights.
  • Suggestions shows open suggestions.
  • Resolved shows closed items, including resolved comments/highlights and accepted or rejected suggestions.

Use the previous and next controls to move between review items. If the document package contains review targets beyond the main content file, the target menu lets you switch between files such as content.md, outline.md, or research.md.

Resolve, accept, reject, or reply

Review actions update both the visible Markdown anchors and the review metadata:

  • Reply adds to a comment or suggestion thread.
  • Resolve closes a comment or highlight without deleting its history.
  • Accept applies the suggested text and closes the suggestion.
  • Reject keeps the original text and closes the suggestion.
  • Delete removes the review item.
  • Assign to me marks you as responsible for following up.

Closed items remain available in Resolved until they are explicitly deleted or excluded by an export mode.

Stale or orphaned review items

A review item can become stale when its text marker is edited or removed outside the normal review controls. The Review rail calls this an anchor issue.

When that happens:

  • Comments and highlights can usually be re-anchored to a new text selection.
  • Suggestions that lost their text marker cannot be safely accepted or rejected; remove the stale item and create a new suggestion.
  • Malformed review markers are preserved until you choose a cleanup action, so mdedit.ai does not silently delete review data.

If you see an anchor issue after editing raw Markdown, review the affected item before exporting or sharing the document.

Export and privacy behavior

Review data is preserved only in article packages.

  • ZIP/package exports keep review state, including review markers, review.json, replies, statuses, authors, assignments, and assets.
  • Local-first and offline saves keep review state in the browser while the document is local or waiting to sync.
  • Clean exports and publish outputs such as Markdown, HTML, PDF, DOCX, and publishing destinations strip comments, suggestions, highlights, and review metadata from the delivered file.

Use a package export when another mdedit.ai user or workspace needs to continue the review. Use a clean export or publishing flow when the recipient should receive the final document without review history.

Related