Stop letting your agents write Markdown.

TL;DR

HTML is a richer, more readable output format than Markdown for AI agents, enabling interactive visuals, better specs, and higher user engagement.

Key Points

• 1.Markdown has become a limiting format for AI agents. Thoric from the Claude Code team argues that files over 100 lines are unreadable, and HTML offers tables, SVGs, JavaScript interactions, spatial layouts, and images that Markdown simply cannot match.
• 2.Karpathy independently endorsed HTML as the better agent output. He recommends appending 'structure your response as HTML' to any LLM query, viewing results in a browser, and frames vision as the brain's 10-lane superhighway — making HTML a natural next step beyond Markdown.
• 3.HTML enables richer planning and exploration workflows. Agents can generate six distinct UI mockups or three implementation options side-by-side in one HTML file, giving more variety than sequential prompting and producing outputs reviewers actually read.
• 4.Code review and PR writeups benefit significantly from HTML. Thoric attaches an HTML explainer to every PR he makes; it can render diffs with inline annotations, color-coded severity, and flowcharts — things Markdown handles poorly.
• 5.Token efficiency concerns about HTML are largely dismissed. While HTML uses more tokens than Markdown, Claude's 1-million-token context window in Opus 4 makes the overhead negligible, and higher engagement means better overall output quality.
• 6.One-off throwaway HTML tools are a powerful but underused pattern. The presenter argues 70%+ of code written today gets discarded after one use — building custom HTML editors with import/export buttons to feed data back into agents is a high-leverage workflow.
• 7.HTML has real downsides: noisy diffs, mobile issues, and token bloat. Version control diffs are hard to review, the sample HTML files weren't mobile-responsive despite claims, and the novelty effect may inflate perceived value — full Markdown abandonment is called 'a little insane.'
• 8.MDX and React-based outputs are flagged as the logical next step. The presenter dismisses a simple /html skill in favor of a more structured primitive, suggests MDX is an untapped market, and hints at future videos exploring HTML skills and Matt Pocock's skill set.