openwiki

Guide · HTML plans

Claude Code HTML plans: why HTML is replacing Markdown for visual specs

In May 2026, Claude Code engineer Thariq Shihipar demonstrated a planning workflow built around rich HTML artifacts: visual brainstorms, implementation specs, temporary editing interfaces, and living design systems. The point was not that HTML makes the Agent smarter; it makes the human more likely to inspect the work closely.

Updated August 3, 2026Practical guide

Where the HTML plan idea came from

The phrase became prominent through a How I AI conversation recorded at Anthropic’s Code with Claude event. Shihipar described replacing long Markdown plans with HTML artifacts that people would actually open, scan, and challenge before allocating more Agent compute.

What HTML adds to an Agent plan

  1. Real visual hierarchy instead of a flat wall of prose
  2. Mockups, diagrams, tables, and code presented in the medium they describe
  3. Side-by-side option comparison
  4. Small throwaway controls for refining one decision
  5. A browser-readable artifact that non-developers can inspect

What HTML does not solve

A beautiful plan can still be too long, unsupported, unsafe, or wrong. HTML source is noisy to diff, embedded scripts increase the security surface, and a local file still lacks a shared identity, formal version history, or approval record. The medium improves human engagement; it does not create governance by itself.

Choose the publication path deliberately

  1. Keep a local HTML file when one person is exploring visually.
  2. Use an HTML artifact host when the exact file must be shared unchanged.
  3. Use a full deployment platform when the artifact is actually an application.
  4. Author a separate typed .mdw plan when the work needs OpenWiki canonical versions, feedback, or a blocking human decision.
Product boundary

OpenWiki Hosted does not accept raw HTML. Do not rename or wrap an HTML plan and imply that it is a supported OpenWiki input.

A governed OpenWiki alternative

This does not preserve arbitrary HTML interactions. It creates a different artifact optimized for deterministic validation, stable revisions, human review, and Agent readback.

# Ask the Agent to author the supported typed plan, then:
ow a2ui draft check ./plan
ow a2ui draft build ./plan
ow a2ui digest ./plan/document.mdw
ow publish ./plan/document.mdw --review --no-open --timeout 900

FAQ

Frequently asked questions

Who proposed using HTML plans with Claude Code?

The 2026 discussion was popularized by Thariq Shihipar, an Anthropic engineer on the Claude Code team, in a How I AI interview filmed at Anthropic’s Code with Claude event.

Can OpenWiki publish a Claude Code HTML plan directly?

No. OpenWiki Hosted accepts validated .mdw packages, not raw HTML. Use an HTML-capable host for the original file or author a separate typed OpenWiki plan.

Is HTML always better than Markdown for Agent plans?

No. HTML is useful when visual structure or interaction materially improves review. Short, diff-friendly text remains better for many implementation notes and repository-native decisions.

Sources and further reading

Use the real workflow

Publish what your agent creates.

Give every report, document, or plan its own reader-ready page. Comments, review decisions, and formal revisions can flow back from there.

Choose HostedSign in