{"slug": "the-workaround-wants-to-be-a-philosophy", "title": "The workaround wants to be a philosophy", "summary": "Claude Code users increasingly output HTML instead of Markdown to leverage richer browser affordances for plans, specs, and reports, but this workaround reveals a missing artifact layer in the product. The practice compresses a six-layer stack into a single view, sacrificing source, review, and export layers critical for team collaboration.", "body_md": "# The workaround wants to be a philosophy\n\nThe work outgrew the transcript. Claude Code could build the missing artifact layer; instead it emits HTML, and the slogan calls the compensation a philosophy.\n\nThariq makes a clean case, and a more careful one than the slogan around it. He keeps code as code, and reaches for HTML on the plans, specs, and reports he actually reads. Long markdown plans are hard to read, and HTML carries affordances markdown cannot. Diagrams. Tables. Sliders. Two-way interaction.\n\nAnd the examples are good. I want to say that first, because it is the part that is true. A brainstorm wants its mockups sitting next to its risk notes. A design system wants to show its colors and type, not describe them. A throwaway micro-app wants real input fields and sliders. The browser is a serious canvas, and Claude can put things on it that a wall of markdown cannot do justice. Anyone who has watched a hundred-line plan scroll past in a terminal feels the pull instantly.\n\nWhat bothers me sits one layer up. The examples are good and the practice is careful. What travels is the slogan, and the slogan is bigger than both.\n\n## The workaround\n\nThe plainest reading of the situation is the one nobody wants to say out loud. Claude Code’s output has outgrown Claude Code’s output surface.\n\nThe model reasons across a codebase, compares approaches, annotates diffs, drafts plans, builds little tools. The human receives most of it as text scrolling past in a terminal. So the user asks the model to emit HTML, opens it in a browser, and lets the browser become the de facto Claude Code UI. The browser is the prosthetic interface for a product that has not grown its own yet.\n\nThat is clever. It is also a tell. The richer affordances are real, and almost every one of them is a browser affordance routed back to the terminal as pasted text. The workaround works. The question is whether it is the destination or a stand-in for one.\n\n## Put the stack next to the slogan\n\n“HTML is the new Markdown” turns an architecture question into a format war. So look at the architecture and decide for yourself.\n\nAgents are not answering questions anymore. They are producing working objects. Plans, specs, reviews, maps, prototypes, reports. A transcript is too small a container for any of that. Underneath the slogan is a real stack, and it has layers.\n\nSource. The durable, diffable thing that travels through git, editors, docs, messages. Markdown lives here, plain on purpose.\n\nState. The structured data the work runs on. JSON and YAML.\n\nView. The rendered surface a human reads and navigates. HTML is excellent here.\n\nInteraction. The surface where the human drags, approves, manipulates a variable. HTML again, sometimes executable.\n\nReview. Diffs, changelogs, provenance, what changed and why. Markdown, because you have to be able to trust it.\n\nExport. The path back to a durable format once the decision is made.\n\nNow read the slogan against that. HTML covers two of the six layers, three on a good day. It is one view over the artifact, and a strong one. The slogan takes that view and prints it on the whole stack. Markdown is not the layer HTML replaces. Markdown is the layer underneath the layer HTML serves. The slogan does not describe the architecture. It compresses it down to the one slice that renders well on a timeline, and drops the rest.\n\nThat is the part I keep returning to. The compression is not free. It costs you source, review, and export, which are exactly the layers a team cannot live without.\n\n## How it breaks\n\nA polished HTML artifact can make a bad plan feel organized. Tabs, cards, severity labels, color-coded sections are persuasive. They produce the feeling that the thinking has been disciplined. Sometimes it has. Sometimes the thought has only been styled. A rectangle is not a proof. An arrow is not causality. A dashboard is not understanding.\n\nThen the reviewability problem the slogan skips. HTML is slower to generate, and its diffs are noise. For a personal exploration that cost is fine. For a team artifact it is not. If a file is hard to diff, it is hard to trust. If it is hard to trust, it is either disposable or dangerous. Markdown is boring here in exactly the way infrastructure should be boring.\n\nThere is a worse one underneath. If nobody wants to read the model’s hundred-line plan, maybe the fix is not to wrap the plan in tabs. Maybe the fix is to ask why the model wrote a hundred lines. HTML can improve comprehension. It can also anesthetize you to bloat.\n\n## The collapse\n\nHis own practice is more careful than his slogan. Code stays code, and HTML carries the plans he reads, so the layers stay where they belong. The slogan keeps none of that scope.\n\nThe crowd is not stupid for liking the examples. They are reaching for orientation. They are tired of unreadable agent output and they want shape and handles. That want is legitimate. The failure is accepting the first shiny compensation as the philosophy.\n\nFor the people building Claude Code inside Anthropic the pressure runs harder. Every internal practice ramps to public artifact within a day. The private workaround becomes content the same week. Content becomes paradigm the week after. Other people’s workflows inherit the path-dependency before anyone asks whether the product was supposed to grow this way.\n\nThere is compression that clarifies and compression that corrupts. “HTML is the new Markdown” is the second kind. It takes a true thing about agents needing richer artifacts and flattens it into a winner-takes-all line, because the line travels and the stack underneath is quiet. Quiet things lose the timeline.\n\n## What it stands in for\n\nThe work outgrew the transcript, and the thing standing closest to the missing layer is Claude Code itself. It has the depth to build that layer for real: durable source, structured state, views you navigate, surfaces you act on, a review trail you can trust, a path back out. Emitting HTML is the version of that you can get today by asking nicely. It is a real compensation, and a good one. The mistake is crowning the compensation, because the tool that produced the work is the one that could give the work a home.\n\nThat is what the slogan costs. “HTML is the new Markdown” tells everyone the asking was enough, so nobody asks for the layer underneath. The workaround gets promoted to a philosophy, and the philosophy quietly retires the more interesting project: building the thing the workaround stands in for. Surfaces do different jobs at different moments, and durability and review do not become optional just because rendering is fun.\n\nHTML is not the new markdown. HTML is the compensation. And the tool we keep asking to emit it is the one that could build the layer it is compensating for.\n\nThe wound is real. The bandage helps. But the tool wearing the bandage is the one that could close the wound.", "url": "https://wpnews.pro/news/the-workaround-wants-to-be-a-philosophy", "canonical_source": "https://provi.me/workaround-wants-to-be-philosophy", "published_at": "2026-06-18 00:00:00+00:00", "updated_at": "2026-06-18 12:02:34.597644+00:00", "lang": "en", "topics": ["artificial-intelligence", "ai-tools", "ai-products", "developer-tools", "large-language-models"], "entities": ["Claude Code", "Thariq", "HTML", "Markdown", "JSON", "YAML"], "alternates": {"html": "https://wpnews.pro/news/the-workaround-wants-to-be-a-philosophy", "markdown": "https://wpnews.pro/news/the-workaround-wants-to-be-a-philosophy.md", "text": "https://wpnews.pro/news/the-workaround-wants-to-be-a-philosophy.txt", "jsonld": "https://wpnews.pro/news/the-workaround-wants-to-be-a-philosophy.jsonld"}}