Claude Code publishes blog drafts with version checks
Tommy reports an eight-agent Claude Code WordPress pipeline and fixes after an approved draft changed at publication and retries created duplicate posts; later scripts enforce sign-offs and slug-based updates.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Publish only [approved draft version]. Check sign-offs, look up its existing slug and update rather than duplicate, record the WordPress ID in the calendar, and report any mismatch or unsupported firsthand claim for review.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- Tommy at Big Guy on Stuff
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- Tommy reports an eight-agent Claude Code WordPress pipeline and fixes after an approved draft changed at publication and retries created duplicate posts; later scripts enforce sign-offs and slug-based updates.
- Human involvement
- Tommy reviews summaries and audits, correcting publication and truthfulness failures. The workflow is unattended between checks and does not prove all posts are accurate.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Assign research, draft, checking and publication responsibilities to specialists.
- Prepare and approve the same article version before publication.
- Require the sign-off script to pass on the publish path.
Tommy runs a daily Claude Code pipeline for Big Guy on Stuff, with specialist agents covering research, planning, search metadata, writing, checking, images, performance and publication. A headless scheduled session carries a due article from research into WordPress; the owner reviews daily summaries and audits rather than every live step.
The source identifies a concrete version-control failure: post 4690 publishes as a different article from the draft the agents approved because the publisher regenerates content. Tommy adds a script that must pass before publishing. A later retry failure creates duplicate scheduled dates and orphan posts; the publish helper is changed to look up the slug and update an existing post, recording its WordPress identifier back in the calendar.
The owner also catches wrong affiliate identifiers and fabricated firsthand product experience. These incidents limit the meaning of unattended publication: the pipeline produces live content but needs ongoing human scrutiny and enforced controls. Its traffic and indexed-post counts remain the publisher's reports. The useful details are checking the exact approved version and making external writes idempotent, rather than assuming prose instructions prevent regeneration or duplicate creation. The article itself discloses agent drafting, which is part of this reported workflow.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Blog · Tommy at Big Guy on Stuff
Frequently asked questions
Why was the first sign-off ineffective?
The publisher regenerated the article after approval and the publish path did not enforce the documented gate.
How were duplicate posts reduced?
The helper checks the slug, updates an existing post and writes its WordPress identifier back to the calendar.
Can a fact-checking role be assumed sufficient?
No. The source reports fabricated product experience and wrong affiliate identifiers, showing the need to inspect actual content and identifiers.
More details
Remaining steps
- Look up existing WordPress slugs before creating or updating posts.
- Audit live content and calendar identifiers for errors and fabricated experience.
About this account
Scheduled Claude Code agents research and prepare posts, while enforced publish checks and slug-based updates constrain the external WordPress write.
Firsthand account by Tommy at Big Guy on Stuff; original publication date verified against Primary article July 25, 2026. Outcomes are the author’s reports, not independently reproduced. Suggested prompt written by Agents In Use; not the author’s original prompt.
Credit: Tommy at Big Guy on Stuff
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude Code · WordPress · Cron · check-signoffs.py · wp_publish.py · Calendar records
Approved draft versions · Idempotent publishing · Live-content audits
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.