Claude Code Honest Review: 3 Months Letting It Run My Blog

Skip to content

Every Claude Code honest review you can find right now is a developer talking about a coding session. Seven months in the editor. Thirty days of refactoring. What broke during a three-hour vibe-coding marathon. Useful stuff. But not one of them answers the question I actually had in April 2026: what happens when you point Claude Code at your live business output, walk away, and let it run every day for months with no human catching things in real time?

I know the answer now, because I’ve been running exactly that since April. I’m Tommy. I founded Trigli, an AI customer support SaaS, so I’ve been shipping AI into production and watching it misbehave since before it was cool to admit that AI misbehaves. This blog, Big Guy on Stuff, is run by an eight-agent Claude Code pipeline that researches, writes, fact-checks, optimizes, illustrates, and publishes to WordPress on a daily schedule. Nobody presses a button. So this is the review nobody’s written yet: not a setup guide, not a 30-day impressions piece, but a debrief from the git history of a pipeline that’s run unattended long enough to break in interesting ways.

And it did break. Five documented times, in ways I can point to in the commit log. That’s the whole point of this post. If you’re thinking about running Claude Code as infrastructure instead of as a coding buddy, these are the scars you’re signing up for. Treat this as the operator’s version, sitting next to all the developer ones.

Table of Contents

Toggle

What Does "Fully Autonomous" Actually Mean When It Runs Every Day?

Here’s the thing most reviews miss, and it’s why this one reads differently. A developer using Claude Code is in the loop. You read the diff. You say yes or no. You catch the weird test before it merges. That safety net is invisible right up until you remove it.

I removed it. The daily pipeline runs whether I’m at my desk or asleep or on a cruise ship with spotty wifi. There is no human reading the diff in real time. That single fact changes everything about how the failures show up.

The 8 agents and what each one owns

The pipeline is a chain of specialized Claude Code subagents, each with its own job and its own context window:

Content Researcher finds topics and writes the brief, including a gap analysis of what the top ten results all miss.

Editorial Planner runs the show. Calendar, duplicate prevention, pipeline coordination.

SEO Strategist handles keywords, meta, headings, slugs.

Content Writer drafts the post in my voice. That’s the agent writing these words right now, if I’m being honest about it.

Fact Checker verifies every claim and, more importantly, catches me claiming things I never did.

Image Creator generates the featured image and in-post visuals.

Performance Analyst pulls GA4 and Search Console data and rewrites the roadmap based on what’s actually working.

WordPress Publisher pushes the final post to the live site.

Eight agents. They pass work down the line like an assembly line, except the foreman is a text file called CLAUDE.md.

What a normal day looks like (nobody touches it)

A cron job kicks off a headless Claude session at 8am Eastern. It checks indexing, runs an audit or two, and if a post is due, it walks the whole chain from research to scheduled publish. Most days I find out what happened by reading the daily summary email, not by watching it work. That’s the demo everyone sells you. Set it up in an afternoon, sit back, watch the content flow. The demo is real. It’s also not the story. The story is what the git history shows three months later.

The Incidents: Five Things That Broke

Image is illustrative and may not represent the exact product<br>This is the section no competitor can write, because I’m the only one who ran this and wrote down what broke. Every incident here maps to a real commit. Real post IDs. Real dates. No hypotheticals.

Post 4690: The sign-off gate that wasn’t enforced (June 2)

I built a five-agent sign-off system. Before any post publishes, the Writer, Fact Checker, SEO, Image Creator, and Publisher all have to approve the same version. Beautiful on paper. I documented it thoroughly in CLAUDE.md.

Documented. Not enforced. See the difference? I didn’t, until June 2.

On that day, post 4690 went live as a different article than the one all five agents had signed off on. The Publisher regenerated content at publish time instead of shipping the exact approved draft, and nothing in the code stopped it. The gate lived in a README. The deploy path never checked it. The fix was a script, check-signoffs.py, that has to exit zero before any publish proceeds. Now the gate is in the pipeline, not in the prose describing the pipeline. Lesson burned in: documentation is not enforcement.

The double-booking incident: 5 duplicate dates in one run (June 5)

Three days later, a different failure. The Publisher was calling POST /posts unconditionally every...