Run tasks on autopilot
Automations run coding tasks on a schedule. Daily cleanups, weekly dependency updates, nightly test suites. Set it once and let agents handle the rest.
How it works
Three steps. No infrastructure. No cron servers to manage.
Create
Give your automation a name and a prompt, the same way you'd describe any task. Tell the agent exactly what to do.
Schedule
Pick a preset like daily, weekly, or weekdays, or write a custom cron expression. Set the timezone and choose your model.
Review
Each run creates a normal task. Review the diff, create a PR, or send feedback, just like any other Capy task.
FAQ
Common questions about Capy automations.
How is an automation different from a regular task?+
An automation is a task that runs on a schedule. Each time it triggers, Capy creates a new task with your prompt, on the branch you configured. You review the output exactly like any other task: check the diff, create a PR, send feedback.
What schedule options are available?+
You can choose from presets (every day, every weekday, every week on a specific day, every N hours, every N minutes) or write a custom cron expression for full control. All schedules respect the timezone you set.
Can I use Captain for automations?+
Yes. You can choose between Build (for direct coding tasks) and Captain (for planning and delegation). Captain is great for recurring analysis, architecture reviews, or multi-step workflows.
What happens if an automation run fails?+
Failed runs appear in the run history with their status. You can review what went wrong, adjust the prompt, and the next scheduled run will try again with your updated instructions.
Can I pause an automation temporarily?+
Yes, just toggle the automation off without deleting it. All configuration is preserved. Toggle it back on whenever you're ready.
Set it and ship it
Put your recurring work on autopilot. Create your first automation in under a minute.