Background Workflows
Work that runs
while you sleep.
Schedule repeat work and choose where the result goes, with the same visibility and approval controls as an interactive task.
- Next run
- Monday 9:00 AM
- Delivery
- Slack #reports
Work on a schedule
Recurring work runs on a schedule. Slack delivery. Approval gates. No manual kick-off.
Durable scheduled triggers
Automations run through the same command lane as interactive work. Each run is durable, visible in history, and cancellable. New automations start disabled: you must explicitly enable.
MCP automation tools
list, get, schema, create, update, run-now, history, delete: all available as MCP tools. Agents can create automations programmatically (with human confirmation for enable).
Slack delivery
Results post to Slack automatically. Outbox-based delivery with durable retry and idempotency. Approval cards appear in Slack too: approve right there.
SEE IT WORK
One agent. Real tasks.
UseAgentExample workflowOur widget service returns 500 on DELETE /widgets/:id when the widget has 3 or more linked components. Fix it.
Clone and search
Cloned repo, found DELETE handler in handlers/widgets.ts. Searched error logs. Every 500 has 'permission check failed' after component count check.
Reproduce locally
Set up test DB with 3 linked components, sent DELETE request, confirmed 500. Traced the stack: permission middleware runs after cascade check, causing the 500.
Fix the order
Moved permission check before cascade. Added test case: DELETE with 3+ components now returns 204. Old test suite still green.
Open PR
Created PR #487: 'Fix widget delete with linked components'. Added test case to prevent regression.
Questions, answered.
What happens if a run fails?
It's logged in history with the error. You can see why it failed and manually re-run. Future: automatic retry policies.
Can I change the schedule without recreating?
Yes. Edit the automation to change cadence, timezone, skill pins, or delivery target. Active runs aren't affected.
Does an approval-gated automation delay the run?
Yes. If the automation calls an operation that needs approval, the run waits. Approval card posts to Slack. Once approved, the run resumes.
Start with one task.
See what you can hand off.
Explore a completed run, or join the early-access list to hear about getting your team started.