Using Claude Code: The unreasonable effectiveness of HTML

May 20, 2026 · 5:26 AM UTC ·19 min read · 0 reactions · 0 comments · 48 views

TL;DR · WeSearch summary

The Claude Code team has shifted from using Markdown to HTML for producing outputs. This change is driven by the desire for richer visualizations and easier sharing of content. The team finds HTML to be more effective for their needs as agents become more powerful.

Key facts

▪Markdown has been the dominant format for communication but is increasingly seen as restrictive by the Claude Code team.
▪The team prefers HTML for its ability to create richer and more readable outputs.
▪HTML allows for better visualizations, color, and diagrams compared to Markdown.

How this story was covered

2 outlets in our directory ran this story, first to last over 30 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.

Centre · 1

▪ I realized I was only using half of what Claude Code has to offer — DEV.to (Top)

About this source

Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.

All Hacker News (Newest) coverage →

Original article

Claude

Read full at Claude →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	Claude
Canonical URL	https://claude.com/blog/using-claude-code-the-unreasonable-effectiveness-of-html
Publication time	Wed, 20 May 2026 05:26:10 +0000
Retrieval time	2026-05-20T05:34:59.850Z
Last seen	2026-05-20T05:34:59.850Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	EoxCopRdn2g7 · 2 stories
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

Using Claude Code: The unreasonable effectiveness of HTMLHow and why members of the Claude Code team use HTML instead of Markdown to produce richer, more readable, and easily shareable outputs.‍ .button_main_icon { transition: color 300ms ease; } .button_main_wrap:hover .button_main_icon { color: var(--_button-style---icon-hover); } .button_main_wrap:focus-within .button_main_icon { color: var(--_button-style---text-hover) !important; } .button_main_wrap:focus-within { color: var(--_button-style---text-hover) !important; } .button_main_icon { transition: color 300ms ease; } .button_main_wrap:hover .button_main_icon { color: var(--_button-style---icon-hover); } .button_main_wrap:focus-within .button_main_icon { color: var(--_button-style---text-hover) !important; }…

Excerpt limited to ~120 words for fair-use compliance. The full article is at Claude.

Anonymous · no account needed

Discussion

0 comments