Is the Way AI Writes Documents Changing? The Era of Chatting via 'Web Pages' Instead of Text

Imagine this. You go to work in the morning and ask your AI assistant, “Organize the materials for this afternoon’s new product planning meeting.” Until now, AI has responded in plain text—black text on a white background, at best mixed with bold text or bullet points (•). We had to copy that text, move it to PowerPoint or Word, and then go through the tedious post-processing of drawing tables and coloring them ourselves.

But what if the AI didn’t just write text, but instantly created and showed you an entire “web page” complete with clickable buttons, colorful graphs, and a sophisticated layout? You would just pull up the screen and start the meeting right away.

This way of communicating has recently become a hot topic among Silicon Valley AI experts. There is a movement to receive AI responses in “HTML,” the language used to build internet websites, rather than a simple text format. Why is this change happening? What does it mean for the general public?

Why It Matters

When we’ve talked to AIs like ChatGPT or Claude, the default format they return has been “Markdown.” Markdown is a very simple and lightweight way to write text. Anthropic’s Claude has even shown a surprising ability to draw crude tables or diagrams within Markdown files by combining special characters (ASCII) [Using Claude Code: The Unreasonable Effectiveness of HTML]. Markdown has established itself as the dominant file format for AI agents because it is lightweight, opens well in any environment, and above all, is very easy for humans to read and edit [Using Claude Code: The Unreasonable Effectiveness of HTML].

But the world is changing fast. As AI gets smarter, people are starting to demand something closer to a “final product” rather than just a “draft.”

If Markdown is a text-centric, static “document,” HTML is a “comprehensive art form” that can contain colors, images, and even dynamic movement. This small difference in format is important because it’s a clear signal that the way we use AI is shifting from “writing assistant” to “creator of finished applications and content.”

Using HTML allows for complex data visualization, interactive functions that can be manipulated two-way, and rich output that is easy to share with others immediately [TheUnreasonableEffectivenessofHTMLinClaudeCode: Why…]. You no longer need to copy and refine the AI’s answer; it can function as a finished report, design draft, or even a small program in itself. This is opening a new era where not just developers, but also the general public who know nothing about coding, can immediately realize their imagination into visible results.

The Explainer

To understand this situation more clearly, let’s use an analogy.

Simply put, Markdown is like a neat “memo” written on office Post-its or a lined notebook. The core content is well-organized, and you can underline with highlighters (bold) or number items. Anyone can easily recognize it, and it’s easy to correct. However, the notepad itself is a bit plain to use as final presentation material.

On the other hand, HTML is like a “high-end interactive magazine” printed in full color that even makes sounds when you press a button. Thanks to its brilliant colors and well-structured composition, it can catch people’s attention at a glance.

In the past, because AI’s skills were a bit clumsy, if the AI provided the skeleton (draft memo), humans had to take it and package it nicely (make it a magazine) themselves. So, the “Markdown” format, which is easy for humans to read and edit, was clearly the best. But now, AI agents have become so smart that they are taking on the heavy burden of content creation themselves. The need for humans to manually edit AI’s output has almost disappeared [UsingClaudeCode:TheUnreasonableEffectivenessofHTML]. If humans don’t need to edit it, the argument is that it’s much more beneficial to output the results entirely in HTML, which can express much more diverse and rich diagrams and colors from the start [UsingClaudeCode:TheUnreasonableEffectivenessofHTML].

Want another analogy? Suppose you want to own a nice car. In the past, you asked the AI to “draw a complex blueprint for building a state-of-the-art car factory (web framework code).” It was too grand and complex, took a long time, and was easy to get lost. But clever developers soon realized: it’s a much faster and more efficient way to reach the goal by simply asking, “Just make me one rolling car (pure HTML) that can run on the road right now” [ClaudeCodeJust SolvedHTMLin Ways We… | Cynthia Media].

Where We Stand

The person who sparked this interesting debate is Thariq Shihipar, an engineer who leads the “Claude Code” development team at Anthropic. In May 2026, he published a provocative and charming essay titled “Using Claude Code: The Unreasonable Effectiveness of HTML,” arguing that requesting HTML instead of Markdown as Claude’s output format is “unreasonably effective” [UsingClaudeCode:TheUnreasonableEffectivenessofHTML], [HTMLvs Markdown inClaudeCode: Why Anthropic’s Thariq Changed…].

Thariq asserted that when putting modern AI agents to work, the era of Markdown is fading and the era of HTML is arriving [Anthropic Engineer Sparks Debate: HTML Is the New Markdown …]. To support his claim, he released 20 complete HTML examples showing how HTML is practically used in actual work environments—increasing information density, enabling interaction, and serving as proposals, code reviews, and design prototypes [TheUnreasonableEffectivenessofHTMLinClaudeCode: Why…], [Anthropic Engineer Sparks Debate: HTML Is the New Markdown …].

The impact of this article was truly enormous. It immediately took the #1 spot on “Hacker News,” a community where the world’s top developers gather, causing a massive shift in perception about how humans consume AI output [Anthropic Engineer Sparks Debate: HTML Is the New Markdown …]. On social media like X (formerly Twitter), posts praising the advantages of HTML—maximizing clarity and interactivity—spread widely, telling people “don’t stay in boring Markdown anymore” [Using Claude Code: The Unreasonable Effectiveness of HTML].

But not everyone welcomed this opinion with open arms. Serious counterarguments are also being raised. The biggest concern is that “co-authoring” between humans and AI could become extremely difficult [Using Claude Code with HTML: Why It Works—and the Co …].

Looking at the discussion on Hacker News, one developer confessed, “It might be faster for me to manually write a complex HTML table than a Markdown table. But in other cases, no matter how much AI automates it, it’s too difficult to maintain a smooth writing flow while looking at pure HTML code” [Using Claude Code: The unreasonable effectiveness of HTML …].

In other words, there is a dilemma: while the visible results become beautiful, the process of a person looking “under the hood” (at the code) and modifying it together is hindered because the code becomes too complex.

In fact, even Thariq, who led this trend, mentioned that to read the agent’s long and complex HTML output, he has to use developer tools like VIM or the MacOS Quicklook feature connected to special extensions, or paste it somewhere else to properly understand the content [UsingClaudeCode:TheunreasonableeffectivenessofHTML]. Technical barriers to entry still exist for the general public.

What’s Next

Despite these pros and cons, developers and users are already rapidly adapting and evolving. In the community, a culture of curating and sharing effective prompt configuration files as templates to induce AI to generate perfect HTML at once is actively spreading [ClaudeCodeHTMLPrompts & GPT-5.5 API Cost… - DEV Community]. Also, YouTube tutorials teaching advanced features and workflows for masterfully handling Claude Code are pouring out [MasteringClaudeCodein 30 minutes - YouTube].

In the future, this scalability is expected to grow beyond text into the media realm. For example, some predict that using Codex or Claude Code, users will be able to immediately generate audio content in podcast form and import it directly into Spotify, the world’s largest music platform, making the form of output even more diverse and multi-dimensional than just web pages [UsingClaudeCode:TheUnreasonableEffectivenessofHTML].

As a result, while “Markdown” will likely survive for everyday short conversations or notes, requesting “HTML-based output” is likely to become the new common sense for tasks requiring complex reports, proposals, and visual materials. Instead of telling AI “explain it in writing,” we will now confidently demand, “Show it to me as a cool web page, and let me click it.”

AI’s Take

When the format changes, our way of thinking changes too. As AI breaks out of the narrow prison of flat text and gains the wings of interactive web technology (HTML), we have reached a point where we should treat AI not as a simple “typewriter,” but as a living “independent content producer” and a “canvas” with infinite possibilities.

The transition from a format that is easy for humans to read and edit to a format where machines can pump out the best visual results is a powerful signal that AI has moved beyond being a simple “assistant writer.” The next prompt we throw will not just stop at creating sentences, but will create entire worlds that people can directly touch and experience.

References

1. UsingClaudeCode:TheUnreasonableEffectivenessofHTML
2. TheUnreasonableEffectivenessofHTMLinClaudeCode: Why…
3. UsingClaudeCode:TheUnreasonableEffectivenessofHTML

4. [ClaudeCodeJust SolvedHTMLin Ways We…

   Cynthia Media](https://media.cynthiaconcierge.com/using-claude-code-the-unreasonable-effectiveness-of-html-tool-drop/)

5. HTMLvs Markdown inClaudeCode: Why Anthropic’s Thariq Changed…
6. ClaudeCodeHTMLPrompts & GPT-5.5 API Cost… - DEV Community
7. UsingClaudeCode:TheunreasonableeffectivenessofHTML
8. UsingClaudeCode:TheUnreasonableEffectivenessofHTML
9. MasteringClaudeCodein 30 minutes - YouTube
10. Using Claude Code: The unreasonable effectiveness of HTML …
11. Using Claude Code: The Unreasonable Effectiveness of HTML
12. Using Claude Code: The Unreasonable Effectiveness of HTML
13. Using Claude Code with HTML: Why It Works—and the Co …
14. Anthropic Engineer Sparks Debate: HTML Is the New Markdown …