Field Note: Markdown Fits the Agent Era
Now more than ever (and 20 years on) Markdown might be one of the most useful skills you can quickly learn. But not for the reason most people think. It’s not about formatting text. It’s because Markdown turns out to be a near-perfect interface between humans and agents.
The Quiet Shift
Tools like OpenClaw and increasingly most AI agents default to Markdown. Not as a feature. As a baseline assumption.
Prompts, tool descriptions, responses, documentation… They all tend to collapse into Markdown-like structures:
- Headings
- Lists
- Code blocks
- Lightweight semantics
That’s not accidental. When I ask Claude to build a definition for an Agent in OpenClaw, it immediately asks if I want a Markdown file.
Why it fits so well
Agents need structure. But they don’t want heavy schemas unless they have to. Markdown sits in a very specific middle ground:
- Structured enough for parsing and segmentation
- Loose enough for humans to write quickly
- Predictable patterns (headings, bullets, sections)
- Composable with other formats (JSON inside code blocks, etc.)
It’s not strict. But it’s legible, to both sides.
A different way to think about it is: If APIs were designed for applications, Markdown is increasingly becoming the interface layer for agent interaction. Not in a formal sense. But in practice. You can:
- Describe tools
- Define intent
- Shape responses
- Embed structured data
…all in a format that survives copy/paste across systems.
The deeper pattern (again). Markdown wasn’t designed for this. It emerged from a simple idea: readable plain text and yet here it is, acting like a de facto standard in agent workflows. The same pattern we’ve seen before:
- Emergence
- Adoption
- Normalisation
- (Eventually) ...Formalisation
On Tools
If you’re leaning into this, Obsidian is the best tool I’ve used to date. It doesn’t fight the format. It lets you operate directly in it. And that increasingly means you’re working in a way that both:
- You understand
- Agents can work with
The implication
This isn’t about learning a syntax. It’s about learning how to express structured thinking in a way that machines can collaborate with. Markdown just happens to be the simplest entry point into that. 20 years on, still simple. But now sitting in a very different place.