I'm thinking of adding support for GitHub-flavored markdown (including things like Mermaid diagrams) in my agent wrapper tool and then adding something like a skill for Claude Code to always write GitHub-flavored markdown and use its features when communicating with me. Seems a lot better than general Markdown.

Though now I'm wondering: why not just add full HTML embedding support as well? I'm talking not just for specific deliverables, but for any of the agent's responses with the user.

Md and plotly is all you need. The only thing that is truly missing is some sort of Markdown-based forms

Have we gone full circle? From the invention of HTML to the rebirth of plain text with MD to the rediscovery of HTML anbrhe age of LLM?

The facts that this article needs to list the pros of HTML over MD, like inreraction, visual density, etc, is weird to me. Maybe the ahdience is not tech-savvy people but I read it as an unnecessary word salad.

(Edit) nvm, the usual Xcancel (https://xcancel.com/trq212/status/2052809885763747935) just links to an article (http://x.com/i/article/2052796100608974848)

This is HTML very much as an output format though.

What happens when my site changes style, I put it back through the LLM I guess and get some bonus hallucinated content.

> I find it difficult to read a markdown file of more than a hundred lines.

Apologies if I'm slightly demeaning here, but what? Markdown is largely plaintext. Unless the output is completely littered with markdown formatting (specifically, imo, tables and maybe links would be the hardest for a human to parse), is this not just saying "I have a difficult time reading large bodies of text" (which is of course fine - people prefer different ways ingesting information)

From reading the post, this seems like a "I personally prefer more visual, interactive elements in output" rather than "agents using markdown leads for less understandable output", and not at all what I would recommend for the average person to use unless said agent or interface or whatever had an extremely seamless way of displaying the HTML. If I had to open the agents response in a browser every time I wanted anything detailed I would lose my mind.

I've certainly had agents generate more rich visualizations such as through html, but I can't imagine using that as my default.

Markdown is not necessarily about presentation. It’s about structure that carries information.

Surely a html page could do the same but I would see that as the last step, to give to someone else.

I’ve also realized CC is exceptional on html, creating local apps for reviewing output, dashboards sourced from DuckDB, etc.

To review PRs in a little custom app is a very good idea. Who cares about 1.2x more tokens when clarity is squared?

Nice article!

We’ve been doing this for a couple of months at work for internal memos and decision records, it’s really powerful. I love being able to drop in interactive visuals and more dynamic content. We have a Cloudflare R2-backed Document Store for managing them, and CLI for publishing, and I’m working on an MCP server for long-term discovery and context.

My team kept asking if they could leave comments though, so I built Annotent [1] to help with that, which is also MCP-backed.

1. https://www.annotent.com/

Each one trades a document you'd skim for one you'd actually read — emdash — or does it really? That entirely depends on your preference of course.

Classical overly confident llm bullshitting.