Skip to main content
Automations run recurring tasks in a cloud workspace, independently of your computer. Use them for issue triage, dependency checks, or monitoring connected services. Review their results in the task history and any PRs they produce.

​
Creating an automation

Open Settings → Automations and click New Automation (or start from a template):
  1. Write the instructions, as you would for a regular task.
  2. Pick the agent that runs it.
  3. Set the schedule — a preset, a weekly picker, or a cron expression — and the timezone.
  4. Leave Fork on to have each run work in its own copy of your cloud environment, or turn it off to run in the main environment, for example to keep dependencies and dev servers up to date for every other task. Changing it later starts a new task on the next run.
You can also ask a cloud agent to create an automation in a normal message, or manage schedules from the CLI. Automations pull context from whatever integrations you’ve connected: GitHub issues and PRs, Linear sprints, Slack channels, Notion databases, Sentry errors, GCP and AWS logs.
Automations require a paid plan — see Pricing.

​
Templates

The template gallery on the Automations page ships ready-made recurring tasks, maintained as a community catalog that grows over time. A sample of what’s there:
  • Daily issue triage — scan open GitHub issues every morning: label, prioritize, spawn fixes
  • Error monitoring triage — fetch new unresolved Sentry errors and fix the actionable ones
  • Cloud log error triage — query GCP or AWS logs for new errors and crashes
  • Weekly dependency updates — update dependencies and verify the build still passes
  • Sprint automation — pick up ready Linear issues from the current sprint and start coding
  • Flaky test detection — mine CI history for flaky tests and verify with targeted reruns
  • Stale PR cleanup — nudge, rebase, or close stale pull requests
Every template is editable before you enable it — they’re just task instructions with a schedule.

​
Managing automations

Each automation can be toggled on/off, force-triggered to run now, edited, or deleted. Runs are recorded in task history, so you can inspect their activity and results.
Schedules use standard 5-field cron: minute hour day-of-month month day-of-week.