1d ago

Anthropic engineer Thariq Shihipar switches to Claude-generated HTML

1.6K23.1K2.3K36.9K9.7M

——0——

Thariq Shihipar, who works on Claude Code at Anthropic, switches from Markdown files to Claude-generated HTML for most tasks. He details the workflow in a post, highlighting improved performance via Claude’s code generation for AI-assisted coding. The approach uses LLM wikis with dynamic HTML artifacts to capture structured data for AI agents and enable interactive outputs in workflows like inbox zeroing and deep research. Developers testing HTML-based artifacts repost and discuss the shift.

Original post

BC#505@BCHERNY @TRQ212

Thariq@TRQ212

http://x.com/i/article/2052796100608974848

10:56 AM · May 8, 2026

Cluster engagement

88 snapshots

AI 1000 · 12 actions

POSTEL#852@OMARSAR0 LLM Wikis + HTML Artifacts are insanely powerful. You should seriously consider this in your workflows. LLM Wikis captures all the important information that lets you and your agents do meaningful work. HTML artifacts present that information in interesting ways that allow you to take important actions along with your agents. My HTML artifacts sit on top of my LLM wikis. They are dynamic and are easily extended as needs arise. I have hooked my Artifacts to talk to my agents, and similarly, the agents can talk to artifacts. This has allowed me to build powerful artifacts that reduce my inbox to zero, keep me updated on any topic of interest, fast prototyping, do deep research, design/trigger new experiments, generate figures to improve understanding, schedule research, search relevant information, discover topics, and so much more. What you see in the clip is not a website. It's a simple interactive HTML artifact. HTML artifacts are useful for designers, engineers, researchers, students, and anyone working with agents. Lastly, HTML doesn't replace Markdown. They are a much better combination working together.
LLM Wikis + HTML Artifacts are insanely powerful. You should seriously consider this in your workflows. LLM Wikis captures all the important information that lets you and your agents do meaningful work. HTML artifacts present that information in interesting ways that allow you to take important actions along with your agents. My HTML artifacts sit on top of my LLM wikis. They are dynamic and are easily extended as needs arise. I have hooked my Artifacts to talk to my agents, and similarly, the agents can talk to artifacts. This has allowed me to build powerful artifacts that reduce my inbox to zero, keep me updated on any topic of interest, fast prototyping, do deep research, design/trigger new experiments, generate figures to improve understanding, schedule research, search relevant information, discover topics, and so much more. What you see in the clip is not a website. It's a simple interactive HTML artifact. HTML artifacts are useful for designers, engineers, researchers, students, and anyone working with agents. Lastly, HTML doesn't replace Markdown. They are a much better combination working together.
QUOTESW#206@SIMONW @TRQ212Asking for HTML explanations of things is pretty neat, I tried it just now with the obfuscated Python POC for the new http://copy.fail Linux vulnerability: https://simonwillison.net/2026/May/8/unreasonable-effectiveness-of-html/#trying-this-out https://x.com/simonw/status/2052864605853278715/photo/1
QUOTEDU#787@DERYATR_@TRQ212This is a very powerful and impactful article from Thariq on using HTML instead of Markdown files for AI coding! As a Claude code engineer he uses HTML with Claude, of course, and I will immediately adapt this for Codex. He makes a great case for this.
QUOTEEL#852@OMARSAR0 @TRQ212I prefer to combine both HTML and MD. I have been sharing a few examples of LLM Artifacts like this one: https://x.com/omarsar0/status/2052062654810980618?s=46&t=lM541_vvE8ML-ozRBlFUDg
I prefer to combine both HTML and MD. I have been sharing a few examples of LLM Artifacts like this one: https://x.com/omarsar0/status/2052062654810980618?s=46&t=lM541_vvE8ML-ozRBlFUDg
QuotingThariq@TRQ212
HTML is the new markdown. I've stopped writing markdown files for almost everything and switched to using Claude Code to generate HTML for me. This is why. https://twitter.com/trq212/status/2052809885763747935
QUOTEEL#852@OMARSAR0 @OMARSAR0Another example
QUOTEEL#852@OMARSAR0 My point exactly: https://twitter.com/kepano/status/2052899901810659362
QUOTEEL#852@OMARSAR0 @OMARSAR0My favourite new stack: Agents + MCP + Markdown + HTML “Files over apps” is a vibe!
My favourite new stack: Agents + MCP + Markdown + HTML “Files over apps” is a vibe!
Quotingelvis@OMARSAR0
LLM Wikis + HTML Artifacts are insanely powerful. You should seriously consider this in your workflows. LLM Wikis captures all the important information that lets you and your agents do meaningful work. HTML artifacts present that information in interesting ways that allow you to take important actions along with your agents. My HTML artifacts sit on top of my LLM wikis. They are dynamic and are easily extended as needs arise. I have hooked my Artifacts to talk to my agents, and similarly, the agents can talk to artifacts. This has allowed me to build powerful artifacts that reduce my inbox to zero, keep me updated on any topic of interest, fast prototyping, do deep research, design/trigger new experiments, generate figures to improve understanding, schedule research, search relevant information, discover topics, and so much more. What you see in the clip is not a website. It's a simple interactive HTML artifact. HTML artifacts are useful for designers, engineers, researchers, students, and anyone working with agents. Lastly, HTML doesn't replace Markdown. They are a much better combination working together.
QUOTEEL#852@OMARSAR0 @OMARSAR0More important takeaway: use both Markdown and HTML. Your agents will thank you for it.
More important takeaway: use both Markdown and HTML. Your agents will thank you for it.
Quotingelvis@OMARSAR0
LLM Wikis + HTML Artifacts are insanely powerful. You should seriously consider this in your workflows. LLM Wikis captures all the important information that lets you and your agents do meaningful work. HTML artifacts present that information in interesting ways that allow you to take important actions along with your agents. My HTML artifacts sit on top of my LLM wikis. They are dynamic and are easily extended as needs arise. I have hooked my Artifacts to talk to my agents, and similarly, the agents can talk to artifacts. This has allowed me to build powerful artifacts that reduce my inbox to zero, keep me updated on any topic of interest, fast prototyping, do deep research, design/trigger new experiments, generate figures to improve understanding, schedule research, search relevant information, discover topics, and so much more. What you see in the clip is not a website. It's a simple interactive HTML artifact. HTML artifacts are useful for designers, engineers, researchers, students, and anyone working with agents. Lastly, HTML doesn't replace Markdown. They are a much better combination working together.
REPLYEL#852@OMARSAR0 @OMARSAR0Every day that passes. I am relying more and more on this simple stack: Agents + MCP + Markdown + HTML. I don't use my browser as much anymore, as the HTML artifacts take care of all of that for me. In a sense, these artifacts are hyperpersonalized, which I feel is how every website I visit should be. Forgot to mention that one of my favorite uses for HTML artifacts is actually monitoring stats, results, trends, etc.
Every day that passes. I am relying more and more on this simple stack: Agents + MCP + Markdown + HTML. I don't use my browser as much anymore, as the HTML artifacts take care of all of that for me. In a sense, these artifacts are hyperpersonalized, which I feel is how every website I visit should be. Forgot to mention that one of my favorite uses for HTML artifacts is actually monitoring stats, results, trends, etc.
Replying toelvis@OMARSAR0
LLM Wikis + HTML Artifacts are insanely powerful. You should seriously consider this in your workflows. LLM Wikis captures all the important information that lets you and your agents do meaningful work. HTML artifacts present that information in interesting ways that allow you to take important actions along with your agents. My HTML artifacts sit on top of my LLM wikis. They are dynamic and are easily extended as needs arise. I have hooked my Artifacts to talk to my agents, and similarly, the agents can talk to artifacts. This has allowed me to build powerful artifacts that reduce my inbox to zero, keep me updated on any topic of interest, fast prototyping, do deep research, design/trigger new experiments, generate figures to improve understanding, schedule research, search relevant information, discover topics, and so much more. What you see in the clip is not a website. It's a simple interactive HTML artifact. HTML artifacts are useful for designers, engineers, researchers, students, and anyone working with agents. Lastly, HTML doesn't replace Markdown. They are a much better combination working together.
REPLYEL#852@OMARSAR0 @OMARSAR0For those interested, I will be doing a live session on this topic soon: https://academy.dair.ai/events/cmovobp97000904l5h0n9a2yz Sign up if you are interested in some of the tools we are releasing soon to get you building with all these ideas.
For those interested, I will be doing a live session on this topic soon: https://academy.dair.ai/events/cmovobp97000904l5h0n9a2yz Sign up if you are interested in some of the tools we are releasing soon to get you building with all these ideas.
Replying toelvis@OMARSAR0
Every day that passes. I am relying more and more on this simple stack: Agents + MCP + Markdown + HTML. I don't use my browser as much anymore, as the HTML artifacts take care of all of that for me. In a sense, these artifacts are hyperpersonalized, which I feel is how every website I visit should be. Forgot to mention that one of my favorite uses for HTML artifacts is actually monitoring stats, results, trends, etc.
REPOSTS🌉#255@SWYX @TRQ212HTML is the new markdown. I've stopped writing markdown files for almost everything and switched to using Claude Code to generate HTML for me. This is why. https://twitter.com/trq212/status/2052809885763747935
REPOSTEL#852@OMARSAR0 @OMARSAR0My favourite new stack: Agents + MCP + Markdown + HTML “Files over apps” is a vibe! https://twitter.com/omarsar0/status/2052850591584383177