Why can't I just use Google Docs for Markdown review?

Because the round trip destroys the file. You paste .md in, Google Docs reformats it, you paste it back out, your code fences and tables are mangled. You end up with two documents that claim to be the same thing and aren't.

How is this different from GitHub PR review?

GitHub PR review is a commenting tool for engineers who are already looking at a diff. OMGfixMD is a commenting tool for anyone who can read prose. No repo required. No PR required. No engineering audience required.

Is this safe for confidential documents?

Yes. There is no backend. Your document never leaves your browser. There is no database to store it in, no account to log into. (The site itself loads anonymous page-view analytics from Vercel; your document is never part of those pings.)

Can I use this to review output from Claude, ChatGPT, or Gemini?

That is the most common use. Paste the model's Markdown reply, highlight the specific sentences that need work, leave your notes, copy everything back as one clean Markdown block, and send it back to the model. The model maps your comments to the passages cleanly — no more 'the second bullet under Architecture, not that one, the other one.'

OMGfixMD is a browser-only tool for leaving inline comments on Markdown files. You paste any .md document, highlight passages, attach comments, and copy the full set of comments back out as clean Markdown. It runs entirely in your browser — your document never leaves the browser, no backend, no account.

The OMGfixMD Manifesto · April 2026

Markdown Deserves a Comment Layer

By Elad Diamant, who got tired of pasting Markdown into Google Docs.

Markdown won. The collaboration tools are still pretending it didn't.

Every spec, every README, every LLM prompt, every RFC now starts and ends as a .md file. It's the default export of Notion, the native tongue of every Git host, and the one format humans and models bothered to agree on.

And yet. If you want to leave a comment on one, you still have the tooling of a 2005 WordPress admin.

(More on OMGfixMD — what we built, in an understandable fit of frustration — further down. First, the problem.)

The workarounds are embarrassing

Here's how teams "collaborate" on Markdown in 2026. Brace yourself:

Claude / ChatGPT

The model returns 1,800 words of Markdown. You want to fix three specific sentences. You describe them in prose — "the bullet under Architecture, not that one, the other one" — and the model rewrites the wrong bullet.

Google Docs

You paste the Markdown in. The formatting breaks. You now have two sources of truth and one of them is lying to you.

Notion

Same thing, nicer wallpaper. Round-tripping to .md silently mangles your tables, your code fences, and your dignity.

GitHub PR review

Great for engineers. Hostile to every other human. Nobody in marketing has ever clicked "Files changed" and they never will.

Slack threads with line numbers

The fact that this is a category is itself the indictment.

For fifteen years, the tools that should have solved this were busy building other things. Senior technical writers — people paid six figures to care about clarity — spend their week performing unpaid ETL between products that appear to be contractually obligated not to talk to each other. Every round introduces drift. Every drift causes an argument. Every argument becomes a forty-minute Zoom titled "quick sync." Somewhere, a product manager is inventing a KPI called "documentation velocity" to measure this. We are all very tired.

The gap isn't a missing feature. It's a missing primitive.

What a comment layer actually is

It's the thing Google Docs nailed in 2006 and that Markdown, for reasons nobody has ever adequately explained, never got.

You highlight the exact range. Not a line number. Not "the third paragraph, second sentence, you know the one."
The note sits beside the text. The document stays clean.
When you hand the file off — to the model, to the publisher, to the next human — you hand off the document. Not the document plus fourteen HTML comments and a Slack thread URL.
You can copy every comment out as plain text. No export wizard. No vendor waving goodbye.

This is not a novel idea. This is Google Docs. The novel part is that a decade into Markdown eating software, nobody had actually bothered to do it for .md. A trillion dollars of SaaS poured into everything adjacent — the wiki, the kanban board, the AI assistant that answers from your wiki — and the actual file just sat there, uncommented, waiting. OMG.

We did. That's the whole product.

The bill comes due in 2026

LLMs write in Markdown. Engineers review in Markdown. Docs sites ship Markdown. The product spec three steps before code is Markdown.

You can now generate two thousand words of technical content in forty seconds. Getting four humans to agree on it still takes three days — because three of the four are copy-pasting it into a Google Doc to leave one comment, breaking the formatting on the way in.

A fast review loop on .md is not a nice-to-have anymore. It's the difference between teams that ship with AI and teams that choke on their own output.

What we built

Nobody plans to become the person who builds the comment layer for Markdown. You just find yourself forty-seven minutes into arguing with a language model about whether the word "moreover" belongs in the third bullet, typing "not that one, the other one" for the fourth time, and you notice nobody is coming.

OMGfixMD is the comment layer Markdown should have had since 2014.

The primary loop is LLM-shaped. Your model drafted the file. You want it to fix three specific things. Paste the Markdown. Highlight what needs work. Leave the note. Copy every comment back out as clean Markdown. Paste that reply back into the chat. The model maps your edits to the exact passages — no more "not that one, the other one."

Humans are the strong second case. Your PM, your engineer, your marketing lead — same workflow, same export. The tool does not care whether the next reader has a pulse.

No backend. No database. No account. The document never leaves your browser. We picked those constraints on purpose — because the thing that kills tool adoption in a doc pipeline isn't the feature set, it's the security review. So we removed the part that needs reviewing.

The bet

Formats don't get replaced. They get layers added to them.

HTML didn't kill plain text; CSS added a layer. Git didn't replace code review; GitHub added a layer. Markdown doesn't need a successor — every "Markdown killer" is someone trying to sell you a Notion subscription. It needs its comment layer.

Markdown didn't need replacing. It needed a comment layer. Every team writing more docs than it reads will figure that out eventually — the only question is whether you figure it out before or after your competitors.