Autopilot is the part of pangoling that keeps writing after setup. It picks the next topic from your plan, drafts it in your voice, and schedules it. How far it goes on its own is your choice.
Turning it on
Autopilot starts switched off. Turn it on from the dashboard, or with Start the engine at the end of setup. It stays off until you do.
Before Autopilot can publish to your site, the site has to pass the launch check described below.
The two modes
You pick the mode in Settings, under Autopilot.
| Mode | What happens |
|---|---|
| Approval first | Autopilot writes and schedules. A person marks each piece ready before it publishes. |
| Auto-publish | Autopilot writes, schedules and posts on the due date, with no per-piece sign-off. |
Approval first is the default. Auto-publish needs a connected publishing target, so it stays unavailable until you have one. See Connect your site.
Reviewing drafts
Drafts waiting for you collect in Create. Open one to read it as it will appear, then:
- Approve it. It is cleared to publish on its date. Undo takes the approval back and holds the piece.
- Ask for changes. Say what is wrong in your own words, as you would to a writer. The piece is rewritten against your note in a minute or two and comes back to you. The note is also kept as a standing rule, so later pieces get it right the first time. A rewrite costs the same credits as an article.
- Edit the text yourself, if the fix is small.
- Delete it if you do not want the piece at all. Its topic is dropped from the plan.
A piece in Create does not publish until you decide on it.
You can also review from an AI assistant connected over MCP: the review-queue prompt walks the same Create list. See Use pangoling from your AI assistant.
The launch check
The launch check makes sure articles render properly on your real site before anything publishes automatically.
When you run it, pangoling:
- writes a short test article that uses every common format at once: headings, lists, a table, a code block, a quote and an image,
- publishes it through your own connection, exactly the way a real piece goes out,
- reads the live page back and checks that the title shows once, the category reads in plain words, no date reads in US month/day order, and every format renders,
- checks the page's canonical link and language tag,
- removes the test article where the connection supports deleting a page.
Every item has to pass. If one fails, the report says which one in plain words, so you or your developer know what to fix in the site template.
Run it from Settings with Run launch check. A site that builds from a Git repository can take several minutes to deploy. The check waits for the page to go live and finishes on its own.
The test article carries a noindex request so it never competes with your real pages. On a connection that cannot delete pages, such as a custom webhook, it stays live with that request until you remove it by hand.