In a May 8 post on X, Thariq argued that Claude Code is increasingly better suited to generating HTML than Markdown, making the case that HTML gives AI-produced documents more structure, richer visuals and easier sharing. He also pointed readers to a gallery of examples on thariqs.github.io/html-effectiveness.
Thariq wrote that "Markdown has become the dominant file format used by agents to communicate with us," but claimed that once documents get longer, it starts to feel restrictive. HTML, he suggested, can carry information more effectively because it can handle tables, CSS, SVG, script tags, interactive elements, responsive layouts, images and other material that Markdown struggles to represent cleanly.
A central point in the thread is that these files are often no longer meant mainly for hand editing. Thariq described using Claude-generated output as specs, reference files and brainstorming material, and noted that when edits do happen, they are often made by prompting Claude again. In that setting, he implied, one of Markdown’s biggest advantages loses some of its force.
He outlined several places where HTML appears to fit better: planning documents with mockups and code snippets, code review explainers with rendered diffs and annotations, design prototypes with sliders and controls, reports assembled from multiple sources, and disposable editing interfaces that can export changes back into a prompt or JSON. He also pointed to two-way interaction, linking to a separate playgrounds post on X as an example.
Thariq also claimed HTML is easier to share because a browser can open it directly once it is posted somewhere accessible. He argued that Claude Code has an advantage here because it can absorb broad context from a filesystem, MCPs such as Slack and Linear, browser data through Claude in Chrome, and git history.
The post does not ignore the drawbacks. Thariq wrote that HTML can take "2-4x longer" to generate than Markdown and acknowledged that HTML diffs are noisier in version control. The replies reflected that tension. Some users backed HTML for prototypes, leadership updates, exploratory tools and data-heavy work, while others defended Markdown for code, plans and documentation, arguing that it remains simpler, more standard and easier to review. One commenter also suggested HTML works best when there are "more illustrations than text."
Asked by one user whether Claude Code users in the terminal should simply have it produce files and open them in a browser, Thariq replied: "yeah basically." He also indicated that the post would eventually appear on the Claude Blog.
Source: Thariq on X
