You've probably seen this tweet by @trq212 floating around on Twitter about letting agents write HTML...
An AWS developer argues markdown should be natively supported everywhere — browsers, email, chat — rather than replaced by HTML in AI agent output. For agentic pipelines, rendering fragmentation limits portability and may push teams to standardize on HTML instead.
You've probably seen this tweet by @trq212 floating around on Twitter about letting agents write HTML instead of markdown...
Listed below are some of the reasons mentioned in the article:
Information Density
Visual Clarity & Ease of Reading
Ease of Sharing (to me this is the most compelling)
Thought-provoking piece by Thariq Shihipar (on the Claude Code team at Anthropic) advocating for HTML over Markdown as an output…
The problem Every web project starts the same way. You open a blank file and start typing...
Why agents are reading your HTML wrong, and what we did about it. I was watching an agent answer a...
Watch now | 🎙️ Anthropic's Claude Code engineer on why HTML replaced markdown, building micro-apps for spec editing, living…
The web was built for humans. But AI agents are struggling with it. Traditional approaches — DOM...
Working with Markdown files for content is super convenient. As a developer, it is hard not to like...
