We went from plain text to SPAs and back to plain text because the reader changed

The arc nobody planned

The web started as plain text. Tim Berners-Lee wrote HTML with hyperlinks and that was it. No build step, no bundler, no hydration. Just text pointing to text.

Then we needed interactivity. jQuery gave us dropdowns. Angular gave us SPAs. React gave us a virtual DOM that diffed against itself to render a todo list. We added thousands of lines of JavaScript so humans could click pretty buttons. The browser became an OS inside an OS.

Now the primary reader is shifting from humans to agents. Agents do not care about your animations, hover states, or client-side routing. They care about structured text. So the output is collapsing back to markdown.

Plain text to bloated SPAs to plain text. Full circle.

The agent infrastructure layer

MCPs are the clearest signal the web is being rebuilt for a different reader. An MCP is not a human interface. It is a natural language API for bots to run commands on our behalf. You expose tools, the agent calls them, things happen. No pixels.

Stainless.com goes further. They auto-generate SDKs and MCPs from OpenAPI specs. Your OpenAPI JSON becomes a typed SDK plus an MCP server. For free. The pipeline from API spec to agent interface is automated. No frontend dev needed.

If your service has an API, it can have an MCP. If it has an MCP, agents can use it. The interface layer is plain text all the way down.

Why I built allmd

I built allmd because I kept hitting the same wall. I needed to feed content into an agent, but it was trapped in formats agents cannot read. A PDF. A YouTube video. A webpage drowning in JavaScript.

allmd converts any URL, PDF, video, or audio file into clean markdown. Because agents need markdown, not pixels. That is the whole thesis. The web is full of information locked behind visual rendering, and agents need it as structured text.

The irony is thick. React developers who spent careers building rich visual interfaces are now building tools that output markdown for agents.

The web is being re-read

Every page, every doc, every API is being flattened back to text. The web is being re-read by machines. Not crawled for search ranking. Read for comprehension. Agents consume documentation, parse changelogs, read blog posts, and execute tasks based on what they find.

This changes what matters about your content. Visual hierarchy was for humans scanning a page. Structured text is for agents parsing information. Heading levels, bold text, link labels are semantic signals for a non-human reader.

What this means for builders

If your product cannot be represented as structured text, agents cannot use it. That is already shaping what gets adopted.

This is not a regression. It is a different reader with different needs. Humans need visual hierarchy, whitespace, colour, animation. Agents need structured text, consistent formatting, clear labels.

The builders who get this are already shipping. The ones still debating React frameworks for their dashboard are building for a reader that matters less by the month.