Runtime · Coming Soon
Workers
Workers allow you to schedule recurring agent tasks, run background maintenance jobs, and execute autonomous workloads across cloud environments. Workers will launch alongside the upcoming Hosted Swarm product and paid plans.
Release status
Coming soon with Hosted Swarm.
Autonomous scheduled workers are not active in the current standalone release of Swarm. While the core scheduling and worker execution engine is built into Swarm's underlying architecture, the full worker deployment and management surface will launch alongside Hosted Swarm and our upcoming paid product plans.
This roadmap preview explains how workers operate, how worker jobs are deployed across cloud infrastructure, and how scheduled tasks integrate with hosted compute allowances and custom cloud environments.
Core concept
Scheduled, recurring work without babysitting.
In everyday Swarm usage, sessions are interactive: you provide a prompt, review checkpoints, and approve actions. Workers extend this model to recurring, unattended schedules.
With Workers, you will be able to define jobs that run on a regular schedule—such as daily code health audits, dependency security scans, website freshness checks, or scheduled media rendering—using standard cron expressions or fixed intervals.
cron & intervals
Schedule worker jobs to run every hour, every night at midnight, or on specific days of the week.
workspace context
Workers run inside your defined workspaces with durable history and isolated worktree sandboxing.
structured outcomes
Every run finishes with an explicit structured status: clean routine completion, ready deliverables, attention alerts, or blocked states.
credit pool or BYO keys
Fund runs through your plan's included credit allowance, or connect your own API keys and private compute infrastructure.
Worker deployment
Deploy workers where your workloads live.
Workers need compute capacity to execute builds, run tests, compile media, and process background queues. When Hosted Swarm launches, you will be able to deploy workers into diverse environments:
- Hosted Swarm Compute: On-demand temporary containers billed by the minute from your monthly credit allowance.
- Major Cloud Providers: Connect and deploy workers directly into Google Cloud Platform (GCP), Amazon Web Services (AWS), or Cloudflare.
- Private VPS & On-Premises: Run workers on your own virtual private servers or local workstation nodes via secure SSH or Docker daemon connections.
Safety & control
Automated does not mean unconstrained.
Workers inherit Swarm's strict permission model and verification gates:
policy approval
Before any worker schedule is enabled, you review and approve its exact prompt, tools, schedule, and execution limits.
fenced execution
Runs execute with bounded time limits and memory caps. If a job fails or requires human review, it halts safely without looping.
audit trail
Every scheduled occurrence preserves its complete transcript, diffs, tool calls, and output evidence in your session history.