“Autopilot” is a word that makes people nervous the first time they hear it applied to publishing on their own domain, and they’re right to be nervous — the reasonable question isn’t “what will it do,” it’s “how do I stop it.” Autopilot publishing hasn’t shipped yet, so this is the design we’re committing to in public before the first line goes live, not a feature list for something you can turn on today.
Pause
The plan: pausing stops new drafts from entering the pipeline and stops anything already drafted from moving to the next stage. Nothing already published would get touched — pause is meant to affect what happens next, not undo what already happened. It’s the control we’d expect most people to reach for first, and it’s designed to take effect immediately, not on the next scheduled run.
Take over
The plan: taking over a topic or a draft mid-pipeline is meant to hand editorial control to a human without discarding the work already done — the brief, the draft, and the quality-gate score would all stay attached, but nothing would move forward without a person approving the next step. Even our highest-autonomy setting for publishing is designed to stop at a WordPress draft, never a live post, so “take over” will mostly matter at earlier stages: which topics get picked, which brief gets written, whether a specific draft ships at all.
Roll back a publish
The plan: if something goes live and turns out to be wrong, rolling back should remove the specific change — a page edit, a schema addition, an entry in a data-driven feature — and, for anything with sitewide surface, notify the individual accounts affected during the live window instead of a blanket announcement or, worse, silence. We haven’t shipped a real rollback yet to point you to as proof; when we have one, we’ll write about it here on the blog rather than just claim it happened.
The line we won’t cross
Autopilot, at its most autonomous setting, is designed to stop at a draft in your CMS. We don’t intend to ever build a mode that publishes to a live domain without a human pressing the button — not because the technology can’t do it, but because “it published on its own” is a sentence we don’t want to be true about a tool with our name on it. The pause, take-over, and rollback controls above are meant to sit on top of that one hard line, not instead of it.
One exception worth naming out loud: this blog. Our own posts are drafted and published to hitmind.ai automatically by our internal tooling — nobody presses publish on each one. We took that risk on our own domain, with our own name on it, so that whatever breaks breaks here first, before any of this is pointed at someone else’s site. What ships to customers is the opposite: the publishing path writes a draft to your CMS and stops there, and there is no branch in that code that can set a post live.
