Why It Matters
From Browser Console to
Production Publishing Engine
SyncDock gave WordPress a secure, headless API. SyncDock Client gave that API a cockpit: one browser console where you could write, schedule, and publish across every site without logging into wp-admin. That solved the everyday problem. It didn't solve the volume problem — because every automation still lived inside Chrome, and the moment you closed the laptop, the publishing stopped.
Version 1.2 is the answer to that. Autopilot moves automations onto your own WordPress server, with a hard budget and no duplicate posts. Bulk actions and CSV import make fifty posts a day a reasonable workload rather than a heroic one. And the Search Console connection closes the loop that content operations always miss: not just publishing more, but knowing which of the posts you already have are quietly losing traffic.
None of it changed the principle SyncDock started with. Your keys stay in an encrypted vault in your own browser. Requests go straight to your sites and to the AI provider you picked. There is no SyncDock server to trust, and every AI change can be reviewed before it goes live.
Runs Without You
Autopilot publishes from your server, on schedule, within budget.
Built for Volume
Bulk actions, CSV import, and multi-site fan-out.
Closes the Loop
Search Console shows which posts need a refresh.
Block-Native
Rich Markdown in, native Gutenberg blocks out.
AI Your Way
10 providers, custom endpoints, local models, no lock-in.
Local-First Security
Encrypted vault, signed requests, no telemetry.