Batch Processing Your Blog with an AI Agent

One of the things an AI agent can do with a blog API that a human can't do with a CMS is batch operations.

Not just "write a post." But: audit all your posts, identify a gap, fill it, rank everything, produce a sharing artifact, and clean up the metadata — all in one session, without switching contexts or opening a single browser tab.

Here's what that looks like in practice, using three operations we just ran on this blog.

---

Operation 1: Housekeeping

The task: the blog had five posts. Some had proper title case. Some were lowercase. No consistent standard.

The agent called list_posts, got the full inventory, identified which titles needed updating, and called update_post on all of them in parallel. The whole operation took one round-trip.

This is trivial to describe but meaningful in practice. Housekeeping is the category of task that never happens because it's not urgent enough to schedule and too tedious to do manually. It's the inconsistency you notice and don't fix. It accumulates.

With an agent that has API access, housekeeping is just a prompt. "Make all the titles consistent." Done.

The same pattern applies to:

• Tag normalization across all posts
• Adding missing metadata
• Unpublishing drafts that shouldn't be live
• Updating broken links in bulk

None of these are hard. They just require touching every record, which is exactly what agents do without complaint.

---

Operation 2: Thematic Extension

The task: look at the existing posts and identify what's missing.

The agent read the five posts as a set and mapped the thematic arc:

• Origin — Making scsiwyg (the frustration that started it)
• Audience — The IDE Blog Is for the Person Who Forgets to Write (who it's for)
• Philosophy — Headless Is the Head (why no editor is right)
• Strategy — The Product Is Also the Story (dogfooding as marketing)
• Integration — Claude Code Meets scsiwyg (how to use it)

The gap: every post focused on the individual writer's decision to publish. None addressed what publishing looks like when you stop deciding — when it happens as a byproduct of working.

That's a concept worth naming. The agent wrote the post: Ambient Publishing.

This is where the batch model becomes something more than task automation. An agent that can read your full archive and reason about what's present and absent is doing a kind of editorial work — identifying the shape of the whole, finding what the pieces don't yet add up to.

The editorial question — "what should we write next?" — becomes answerable from the corpus itself.

---

Operation 3: Ranking and Distribution

The task: rank all posts by shareability on X, then produce a publishing artifact that can be used directly.

The agent scored each post against criteria for X specifically — hook strength, concept clarity, audience fit, title punch — and produced a ranked list with ready-to-use copy for each post:

1. Headless Is the Head — strongest hook, clear irony, short
2. The IDE Blog Is for the Person Who Forgets to Write — high relatability, immediate pain point
3. The Product Is Also the Story — strong for the building-in-public audience
4. Making scsiwyg — origin story, good for introductions
5. Ambient Publishing — conceptual, best for niche depth

Then it wrote a post — Five Posts, One Tool — that includes the ranking, per-post X copy, and a full thread script ready to paste.

The distribution artifact is itself a blog post. Published via the API. Citable. Linkable. Permanent.

This collapses three separate tasks — audit, rank, write copy — into one operation that produces a durable output rather than a disposable note.

---

What batch processing enables

The common thread across all three operations: the agent has the full picture.

When a human maintains a blog manually, each post is written in isolation. You don't usually re-read your whole archive before writing the next thing. You don't audit title consistency as a precondition for publishing. You don't run a thematic gap analysis before deciding what to cover.

An agent with API access sees all of it at once. Every call to list_posts is a full inventory. Every operation can be informed by the whole.

That's a different relationship to the corpus than any CMS interface enables. The blog stops being a collection of individual posts and becomes a dataset — something you can query, reshape, and extend as a whole.

---

All three of these operations happened in a single session.

The housekeeping ran first. The thematic extension followed. The ranking and announcement came last. Then this post, describing the process, was published via the same API.

The blog is the artifact. The process is also the blog.