The HTML Pivot: Why AI Agents Need More Than Text
Moving beyond Markdown to build richer, interactive intelligence
For years, Markdown has been the lingua franca of the developer and the writer alike. It is simple, lightweight, and easy for both humans and machines to parse. But as we move into the era of autonomous AI agents, Markdown is hitting a ceiling. When an agent like Claude generates a thousand-line technical specification, a wall of text becomes a barrier to engagement. You don't read it; you skim it, or worse, you ignore it. This is where the shift toward HTML begins. By using HTML as the primary medium for AI communication, engineers are turning static plans into living, interactive artifacts. This isn't about making things look pretty; it is about information density and the ability to actually interact with a plan before a single line of production code is written.
The Rise of the Compute Allocator
The role of the software engineer is undergoing a fundamental change. We are moving away from being pure code writers and toward becoming 'compute allocators'. When an AI agent can run for hours on a single complex task, the engineer's primary job is to decide how to spend that computational budget. You are no longer just typing syntax; you are defining boundaries, setting constraints, and deciding which problems are worth the $500 of compute required to solve them. This makes the planning phase—the specification—the most important part of the workflow. If the plan is a mess of text, the execution will be too. If the plan is a structured, interactive HTML document, the engineer can audit the logic with precision.
The engineer's job is no longer writing code, but deciding what is worth building and how to spend the compute to get there.
This new workflow encourages a 'throwaway' mindset. Instead of building massive, monolithic tools to manage a project, engineers are building micro-UIs—small, bespoke interfaces designed to solve one specific problem, like editing a complex data table or visualising a dependency graph. Once the task is done, the interface is discarded. This abundance of tokens allows for a level of bespoke tooling that was previously too expensive or time-consuming. We are seeing a world where 99% of the AI's output is dedicated to the scaffolding, the interfaces, and the communication, rather than the final product itself.
- Use HTML for interactive, high-density specifications
- Build bespoke micro-apps for specific planning tasks
- Focus compute on planning and verification rather than just production
- Maintain living design systems in code-readable formats
Ultimately, the goal is to keep the human in the loop. The danger of AI is not that it replaces us, but that it makes the work so opaque that we lose the ability to critique it. By moving from text to interface, we ensure that the complexity of the machine remains legible to the person directing it. We aren't just making better software; we are making better ways to think about software.
The value of engineering is shifting from the ability to write syntax to the ability to allocate compute and manage complex, interactive specifications.