{"id":35185,"date":"2026-05-11T21:56:11","date_gmt":"2026-05-11T21:56:11","guid":{"rendered":"https:\/\/www.europesays.com\/ai\/35185\/"},"modified":"2026-05-11T21:56:11","modified_gmt":"2026-05-11T21:56:11","slug":"anthropic-engineer-debates-use-of-markdown-vs-html-in-ai-agent-output","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/ai\/35185\/","title":{"rendered":"Anthropic Engineer Debates Use of Markdown vs. HTML in AI Agent Output"},"content":{"rendered":"

\"Anthropic<\/p>\n

Markdown has emerged as the lingua franca of AI, especially with the proliferation of AI agents. But an Anthropic engineer argues that HTML is a better choice for output. And despite my love of Markdown, I have to say, he makes a compelling case.<\/p>\n

\u201cMarkdown has become the dominant file format used by agents to communicate with us,\u201d Anthropic\u2019s Thariq Shihipar writes<\/a>. \u201cIt\u2019s simple, portable, has some rich text capability and is easy for you to edit. Claude has even gotten surprisingly good at using ASCII to make diagrams inside of markdown files.\u201d<\/p>\n

So what\u2019s the problem? As hinted in that last sentence, Markdown is limited when it comes to output: This is just plain text with some formatting syntax in the form of special characters, and though it\u2019s human-readable, it can\u2019t be made to be as pretty and visual as HTML.<\/p>\n

\u201cI want richer visualizations, color, and diagrams and I want to be able to share them easily,\u201d he adds. \u201cI\u2019ve started preferring HTML as an output format instead of Markdown and increasingly see this being used by others on the Claude Code team, this is why.\u201d<\/p>\n

He\u2019s onto something here. If you know your Markdown history\u2013I write about this in an as yet unfinished chapter in what might become a book about Markdown for writers<\/a>\u2013you know that when John Gruber created it, Markdown was two things: It\u2019s a plain text formatting syntax, and a software tool that converts that plain text formatting to HTML, the language of the web. That is, Markdown was never meant to be the output. The output was always going to be HTML.<\/p>\n

Shihipar explains, correctly, that HTML can convey much richer information than Markdown and that it can be used to create beautiful visuals with images, code snippets, interactive elements with JavaScript, designs with CSS, and much more. \u201cThere is almost no set of information that Claude can read that you cannot fairly efficiently represent with HTML,\u201d he writes. \u201cThis makes it a highly efficient way for the model to communicate in-depth information to you and for you to review.\u201d<\/p>\n

I use Markdown for writing because it\u2019s simple and fast and infinitely compatible, but it\u2019s worth pointing out that the app I use to write, Typora, is visual in nature and provides a formatted representation of what I write using embedded hyperlinks, headline styles, bold and italic text, and the like. But many Markdown editors provide both source code and output displays, often side-by-side. The output display is HTML.<\/p>\n

Shihipar\u2019s post goes into more detail on this topic, but I didn\u2019t have to get too far into it before I realized how right he is. If you think about HTML, there\u2019s a code view with a tags-based syntax that is human readable but not pretty, and then a formatted HTML display. Markdown works the same way, it\u2019s just a lot simpler than HTML. But if you care about this stuff, his post is absolutely worth reading. I\u2019m curious to see what if anything comes out of this.<\/p>\n","protected":false},"excerpt":{"rendered":"Markdown has emerged as the lingua franca of AI, especially with the proliferation of AI agents. But an…\n","protected":false},"author":2,"featured_media":35186,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[53,22321,22320],"class_list":["post-35185","post","type-post","status-publish","format-standard","has-post-thumbnail","category-anthropic","tag-anthropic","tag-html","tag-markdown"],"_links":{"self":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/35185","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/comments?post=35185"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/35185\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media\/35186"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media?parent=35185"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/categories?post=35185"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/tags?post=35185"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}