Review – don't chat

Markleft gives your and your AI's remarks and suggestions on Markdown a place to live: in the document itself.

Install Now 

Video

Finally read those AI Plans

AI rarely gets your intent right on the first prompt. Reading through a wall of text without a place to take notes sucks. You made it through? Great—now you type in your feedback: “Make the third sentence in the second paragraph less technical.” Then it comes back with a new file—you read it again and check whether your prompt was good. That sucks. We can do better!

Markleft gives Markdown comments and suggestions a place to live: in the document itself. Point to the exact text, block, image, table cell, or diagram; explain what matters; then review a proposed change before it becomes part of the file.

Your Markdown remains the source of truth. Your feedback remains attached to the work.

¹

Feedback that keeps its context

Markleft brings back the familiar review loop:

1. Point, don’t describe. Select the exact words or place a marker on an image, SVG, code block, table, or Mermaid diagram.
2. Keep the reason beside the work. Comments and replies are stored as portable Markdown footnotes, so the intent travels with the file.
3. Review the proposal. Suggestions appear in context. Accept, discard, or refine each one instead of comparing an opaque rewrite.

“Make this less formal” is useful only when it stays next to the sentence it refers to.

Built for humans and AI to iterate together

Markleft is a review surface, not another document format or a walled garden.

• Local by default. Open a file from your computer and save it back to the same place. Markleft asks before it receives file access.
• Plain Markdown underneath. Comments use normal footnotes; unaware renderers still show readable notes.
• Suggestions, not takeovers. Proposed edits are explicit and reviewable before they alter the document.
• Works with real documents. Review prose, lists, tables, code, images, inline SVG, and Mermaid diagrams in one file.
• Bring your own assistant. After saving, use the generated instructions with the AI tool you prefer.

Start with the Markdown you already have

Open a local .md, .markdown, or .mdx file with Open Markdown… in the Markleft menu, or press ⌘O on macOS (Ctrl+O on Windows and Linux). You can also drag a Markdown file onto Markleft.

Once the page is installed as an app, Markdown files can open directly from Finder

Install Now

The installed app is optional. The website is already the editor: open a document when you are ready.

A small format with durable review data

Markleft records annotations using Markdown’s established footnote mechanism. A comment has an anchor and a definition; suggestion metadata is appended rather than silently rewriting the original document. Stable block IDs make structural changes addressable when you want them.

This sentence needs a more direct ending.[^range-prev-16-chars-7f3a-a91c]

[^range-prev-16-chars-7f3a-a91c]: Say what the reader can do next.

That means a file remains understandable in GitHub, a text editor, or a normal Markdown renderer — and becomes a rich review workspace in Markleft.

Try a real review loop

Open any Markdown file, leave one precise comment, save, and ask your assistant to address the annotations in the saved document. Markleft lets you inspect each resulting suggestion in context before accepting it.

For the longer story behind the workflow, read How I review Claude plans in Markdown. The source and current prototype are available on GitHub.

Ready when your document is. Use the Markleft menu to open Markdown, or drag a file onto this page.