AI coding tools are getting much better at producing work, but I keep running into a new problem: reviewing the output.
A single task can leave behind implementation plans, API notes, QA checklists, handoff docs, Mermaid diagrams, and HTML previews. These files are often scattered across project folders and mixed with source files, build outputs, logs, and dependencies.
I built MD+HTML Reader as a small macOS app for this review step. It opens a project folder, filters for Markdown and HTML, renders them in read-only mode, and helps you return to recently viewed or changed docs.
I m curious how others handle this today:
MD+HTML Reader
Thanks everyone for taking a look. I really appreciate the attention and feedback.
Feel free to ask me anything in the comments. I will use three quick Q&As below to explain the user pain I am thinking about and where I see the value of MD+HTML Reader.
Q: What problem does it solve?
AI coding tools now generate a lot of useful project documentation: implementation plans, API contracts, QA checklists, handoff notes, and HTML previews. The problem is that these files often live across different folders and get buried under source code, build outputs, logs, and dependencies.
MD+HTML Reader gives you one focused place to review the Markdown and HTML files that actually need attention.
Q: Why not just use VS Code or a browser?
VS Code is great for editing code, and browsers are great for opening web pages. But the review step is different.
When I am reviewing generated docs before the next prompt, commit, or handoff, I want a quieter read-only workspace: open the whole project folder, filter out project noise, preview Markdown and HTML, and keep recent context easy to return to.
Q: What are the most useful features?
The most useful features are project-folder scanning, Markdown/HTML filtering, read-only preview, recent documents, recently changed documents, document-title browsing when filenames are unclear, and quick navigation back to the context you were just reviewing.