Work / 02All work

mdReview

A local Linux application for reviewing Markdown documents made by coding agents.

Built
A browser interface for reading Markdown, commenting on documents or selected text, and saving feedback beside the original file.
Keeps review simple
Comments can stay with a Markdown file without changing the document or moving it into another service.
Role
Independent product engineer
Status
v0.1 release candidate
Period
2026
System
Go · Preact · TypeScript · Playwright · Agent Skills
mdReview interfaceFiles · Markdown · Comments
01 · ReviewLeave a commentComment on the document or selected text
02 · AddressAsk an agent to editThe agent reads the sidecar and changes the Markdown
03 · CheckReview the changeResolve the comment when the work is complete
mdReview showing a Markdown file, selected text and review threads

mdReview is a local Linux application for reviewing Markdown documents made by coding agents. It is designed for plans, specifications and other Markdown files that need human feedback.

Run it against a directory, open the local URL it prints, and choose a file to review in your browser.

How it works

The interface has three panes:

  • Files lists the Markdown files in a directory.
  • Document renders the selected Markdown file.
  • Review shows comments and replies.

You can comment on the whole document or select text and comment on that section. Threads can be replied to, marked as handled and resolved.

mdReview is distributed as a single Go binary with an embedded Preact interface. It runs locally on Linux and does not need a Node.js runtime.

Comments stay with the document

Comments are saved in a JSON sidecar beside the Markdown file:

plan.md
plan.md.review.json

The Markdown file is not changed. The sidecar can be committed or shared with the document when the feedback needs to travel with it.

Markdown files can change after a comment is created. mdReview keeps the original selected text and its exact location. If that location no longer matches, it looks for one exact copy of the original text. If it cannot find one unique match, the comment stays visible but is marked as detached.

Working with coding agents

The sidecar is also how feedback is handed back to a coding agent:

  1. You leave comments in mdReview.
  2. A coding agent reads the sidecar and edits the Markdown file.
  3. The agent marks completed comments as handled.
  4. You review the changes and resolve the comments.

An optional Agent Skill explains this workflow to Codex, Claude Code and Gemini CLI.

What mdReview does not do

mdReview does not edit Markdown, start an agent or send comments automatically. It displays the document and records feedback. The source file and its review data remain in the project directory.

Read first

See how real failures became an evaluation and architecture system.

Read Crispin