I decided I wanted to start blogging. I already had my site up at nathanglass.com with a few project pages, but no blog system. My first instinct was obvious: go to GitHub, find a good CMS, integrate it into the site.
WordPress. Ghost. Strapi. Contentful. There’s no shortage of options.
Then I stopped and asked a different question: who is actually going to be writing and publishing these posts?
Not me. My AI agents are.
The Setup
I run my company using Paperclip.ing where AI agents operate autonomously. My CEO agent handles strategy, delegates work to specialized agents — an Engineer, a Website Designer, a Logo Designer — and they execute independently. The Engineer writes code, pushes to Git, and Vercel auto-deploys.
The entire workflow is agent-driven. I drop raw notes and ideas into Obsidian (my personal vault), and my agents pick them up, draft posts for each platform, and publish when I approve.
The Realization
So I’m looking at CMS platforms thinking about admin panels, content models, rich text editors, media libraries, user roles…
And it hits me: none of that is for agents.
Every CMS ever built was designed around a human sitting at a dashboard. Drag-and-drop layouts. WYSIWYG editors. Preview buttons. Publishing workflows with manual approval steps.
My agents don’t need a dashboard. They don’t need a rich text editor. They don’t need a preview button — they can read the rendered HTML just fine.
“Git Is Our API”
I went back and forth with my CEO agent about this. I suggested we could build a lightweight API — a couple endpoints the agents could hit to add blog posts programmatically.
My CEO agent came back with something better:
“No, we don’t need an API. Git is our API.”
The agent writes a markdown file with frontmatter. It commits to the repo. Vercel rebuilds the site. Done.
No CMS. No database for posts. No admin panel. No API layer. Just files in a repository.
The simplicity is almost absurd compared to what the CMS industry has built over the last 20 years.
What This Means
The entire CMS category — WordPress (43% of the web), Contentful, Sanity, Strapi, all of it — was built on one assumption: a human needs a friendly interface to manage content.
When that assumption breaks, the category breaks with it.
If your content workflow is increasingly automated — AI writing drafts, AI formatting for platforms, AI scheduling posts — then your CMS is overhead. It’s a human interface layer with no humans on the other side.
What agents actually need:
- A file system (markdown files with structured frontmatter)
- A deploy pipeline (Git push triggers build)
- Structured data (YAML/JSON, not rich text blobs)
That’s it. Everything else in a CMS — the dashboard, the editor, the media manager, the plugin ecosystem — is a human convenience layer that agents route around entirely.
The Uncomfortable Question
If you’re building content infrastructure today, ask yourself: in two years, who is publishing?
If the answer is “mostly agents, with human oversight,” then you’re building a human dashboard for non-human users. That’s a product designed for yesterday’s workflow.
The tools that win in an agent-first world are the ones that look more like Git and less like WordPress.