Feature deep-dive
The Auto Agent
Last updated
The blog runs itself when you want it to. Set headlines per week and the days/UTC hours you want articles to ship. The Auto Agent handles the rest: topic selection from AEO recommendations, drafting through the 11-stage pipeline, image generation, publish, and revalidation.
What it does, end to end
- Plans: pulls top-ranked actions from the AEO recommendations engine into the headline queue.
- Schedules: respects your headlines-per-week + days/UTC hours config.
- Drafts: runs the 11-stage pipeline (research → synthesize → outline → draft → reflection → rewrite → metadata → FAQ → embed → images → render).
- Approves (optional): kanban gates can require human approval at any stage.
- Publishes: fires the signed publish webhook, exposes the article on the Reader API, or commits MDX to your repo. Or publishes straight into WordPress or Ghost.
- Revalidates: HMAC-signed webhook fires; your site rebuilds the affected page.
- Indexes: IndexNow, Bing Webmaster, Google Indexing API ping immediately.
- Notifies: lifecycle email if you opted in (article published, weekly digest, quota at 80%).
What stops it
- Thin research or low editorial-critic confidence — the article is held as a draft for you to review instead of being auto-published. (A manual publish from the kanban is your explicit override.)
- You hit the monthly article quota — Auto Agent stops cleanly, sends quota-100 email.
- You pause autopilot in the dashboard.
- Reflection critic fails three times on the same headline — surfaces in the kanban for human review.
- Connected CMS credentials revoke — webhook delivery fails open and the article is held in Drafts.
Questions
Does the Auto Agent need approval before it ships?
Your call. By default it runs autonomously within your monthly quota — with one built-in safety net: any article whose research came back thin or whose editorial-critic confidence is below the auto-publish bar is held as a draft for you to review instead of shipping unattended. On top of that, you can require human approval at the headline stage, the draft stage, the published stage, or none at all. The kanban (Pipeline / Drafts / Published) is the approval surface.
How does it pick topics?
From the AEO scan recommendations engine. Top-ranked actions become the next headlines. You can also seed manual topics that take priority.
What if it makes a mistake?
Reflection critic auto-rewrites anything below 0.8 confidence before it leaves the drafting pipeline. Anything above gets metadata, FAQ, images, and renders. Even after publish, you can edit in the Article Editor or roll back.
Quota?
The Auto Agent stops cleanly at your monthly article + prompt-run cap and sends a quota-80% then quota-100% email. Add-ons let you top up without changing plans.