Funny how I randomly thought: how the heck did .md files end up basically running the show now? Not just in repos as READMEs. They're literally load-bearing walls in the AI ecosystem and I would've laughed if you told me this a few years back.

It's a weird arc for a plain text file.

The README Era

For most of my career, Markdown meant one thing: README files. You wrote one when you pushed a repo. It explained what the project was, how to run it, maybe a quick example. Nobody was precious about it. It was the file you wrote last, usually when you were already done with your project and slightly exhausted.

GitHub made it the default in 2008 and that was pretty much that. It lived in repos. It rendered nicely. That's it.

Nobody sat down and thought: this is going to matter.

And yet here I am, writing this very post in Markdown as this blog runs on Ghost, and Ghost is Markdown under the hood. Even my note-taking app is Obsidian, which stores every single note as a .md file. I've been living in Markdown this whole time without really registering it.

The Quiet Takeover

That thought made me search. And the history is almost too on-the-nose.

John Gruber made it in 2004 because he just didn't want to write HTML by hand. The entire origin story is "this was annoying, let me fix it for myself." Aaron Swartz helped. The first converter was a Perl script.

That's it. That's the founding mythology of what is now, without exaggeration, critical infrastructure.

Stack Overflow shipped with Markdown support in 2008. GitHub made it the face of every open source project. Static site generators ran on it. Note-taking apps adopted it. And then slowly, quietly, it became the format developers just used, not because someone mandated it, but because plain text that renders well is genuinely hard to beat.

It won because it was portable. Humans can read it even without rendering. Machines can parse it easily. Copy-pasting between systems just works. It's not perfect. Not elegant. Just compatible with almost everything.

And then AI showed up.

Plot Twist

AI models output Markdown by default now. Every response, every structured answer, every tool output. Headers, bullet points, bold text, code blocks. All of it formatted in a syntax that one blogger invented because he hated angle brackets.

Agents read it. Agents write it. Headings become context boundaries. Bullet points become instructions. Code fences become executable blocks. Systems are being built where .md files are the interface between humans and AI, the thing you edit to change how an agent thinks, what it knows, what it does.

SKILL.md. AGENT.md. README.md as configuration.

It's not a document format anymore. It's an instruction layer.

The format is simple enough for humans but structured enough for machines. That balance is surprisingly rare. And that's exactly why it stuck.

Kind of Wild

Gruber didn't design it for agents. He designed it to get out of his own way while writing. And now that's exactly why it works, because it carries meaning without ceremony. No tags. No schemas. No overhead.

The trillion-dollar AI industry is running on a plain text format someone made for their blog in 2004. Not because it was engineered for this. Because it was simple enough to survive everything.

I don't know what that says exactly. But I find it kind of wild.