A Talos workflow is a prompt plus a trigger plus a fixed set of permissions. You describe the outcome in plain language, choose when it should run, and lock down exactly what it is allowed to do. Drafts never run until you enable them.
Schedules run once, daily, on weekdays, weekly or monthly in your site timezone, queued by WP-Cron. Hook triggers fire on a WordPress action — content, comments, users, plugins, themes, media or options — so work happens when something actually changes.
Enabling a workflow stores its pre-authorized action scopes. A scheduled run executes inside them and cannot widen them, add tools, or change the report recipients — which is what makes unattended running safe.
A headless runner executes workflows as jobs with token-based leases, heartbeats, checkpoints and cancellation. They survive a closed browser, and hook triggers carry cooldowns and concurrency limits so a burst cannot stampede.
Email delivery uses wp_mail to up to ten fixed recipients, with durable idempotent delivery records. Because the agent cannot change the To field, content it reads during a run cannot redirect a report elsewhere.
Once · Daily · Weekdays · Weekly · Monthly
WordPress site timezone
Minute cron tick, queued by WP-Cron
queued · running · retry · awaiting approval · completed · failed · cancelled
Up to 10, fixed at enable time
30 runs per hour by default
Nothing. Drafts have no schedule and no scopes, and they do not run. Drafting is deliberately separate from enabling so the agent can propose automation without creating it.
It is recommended for low-traffic or time-sensitive sites. WP-Cron only fires on requests, so a quiet site can leave a 09:00 workflow waiting. Disable request-driven WP-Cron and point your server scheduler at wp-cron.php every minute for reliable timing.
Yes — awaiting_approval is a job status. A run that hits an action beyond its scope or above the approval threshold pauses rather than proceeding or failing outright.
Put recurring WordPress work on a schedule. Talos runs scoped workflows in the background, emails you a report, and never expands its own permissions.
Read moreModes, per-tool policy, approval gates, roles and budgets.
Read moreSuccessful tool sequences compiled into reviewable, replayable skills.
Read moreSpend less time clicking through admin and more time moving your site forward.
