How to schedule Devin CLI: cloud Automations vs local runs

By CodeAgentSwarm · Updated October 31, 2026

Devin can run on a schedule, but in Devin's web app: Automations start cloud sessions on a timer or on events. Devin CLI, which works in your local project, has no schedule command. This guide covers both and shows how to schedule the CLI on your machine.

Can Devin CLI run on a schedule?

Devin CLI
  • Devin cloud: yes, with Automations (schedule, Slack, GitHub, Linear or webhook triggers).
  • Devin CLI on your machine: not by itself. Use cron with devin -p, or CodeAgentSwarm.

Devin Automations and scheduled sessions

Automations can repeat every N minutes, hours, days, weeks or months, follow an RRULE, or run once. The default limit is 50 runs per hour, and you can cap the compute (ACUs) a session may use. Devin Automations. The older scheduled sessions are a legacy feature that keeps working; new scheduled work is created as an automation. Scheduled sessions

The Devin CLI command reference has no schedule command, so Automations are a Devin cloud feature, separate from the CLI you run in a local folder.

A Devin CLI cron job with devin -p

bash
# crontab -e: weekdays at 08:00
0 8 * * 1-5 cd ~/code/my-app && devin -p "Run the tests and explain failures. Do not edit files." >> ~/logs/devin-cron.log 2>&1

Print mode cannot show the workspace trust prompt, so in a folder Devin does not trust yet it fails; Cognition documents --respect-workspace-trust false to skip that check in scripts. Devin CLI commands Keep the default permission mode for unattended jobs unless the project is disposable.

Schedule Devin CLI in CodeAgentSwarm

  • Open Scheduled in the top bar and press New schedule. Or type the prompt in a Devin CLI Chat and pick Schedule this prompt… from the send menu.
  • Pick the Project and choose Devin CLI as the agent. Model, reasoning and permissions are optional: leave them on Default or set them like in the Chat composer.
  • Write the prompt the agent should run every time.
  • Under When, choose At set times (up to 24 a day), Every few hours (1, 2, 3, 4, 6, 8 or 12) or When I run it, and the days.
  • Choose Visible (opens a Chat) or Headless (no tab, result in Scheduled), and whether each run continues the same conversation or starts a new one. Press Create schedule.
CodeAgentSwarm schedule editor set to At set times, Every day at 21:00, with the next three runs and the Visible option
The editor shows the next runs before you save. Real capture from CodeAgentSwarm 2.5.0.

Prompts worth scheduling with Devin CLI

  • Every weekday at 08:00: run the tests in this local checkout and explain anything that fails.
  • Every 8 hours: read the local log folder and summarise new errors.
  • Fridays at 17:00: list the files changed this week that have no test coverage.

What happens on each run

  • With Continue the same conversation, a visible run goes to the Devin CLI agent that already holds the conversation, and never opens a second copy. With Start a new conversation, each run opens a fresh agent. If it is busy, Skip if still working (on by default) skips that slot; turn it off and the prompt waits in the queue.
  • The Chat marks every scheduled run, so you can tell your own messages from the scheduled ones and reply to a run like any other message.
  • If CodeAgentSwarm was closed or the computer asleep at the set time, If missed, run when the app opens runs it once, late. A week away gives one run, not seven.
  • Schedules run on your computer, so CodeAgentSwarm has to be open. Your phone can list, edit and run them from the Scheduled tab.

FAQ

Can Devin run on a schedule?

Devin cloud can, with Automations. Devin CLI has no schedule command; run it from cron or CodeAgentSwarm.

Do Devin Automations use my local files?

They start Devin sessions, not your local CLI. To work on your local checkout, schedule Devin CLI on your machine.

How do I run Devin CLI from cron?

Add a crontab line that changes to the project and runs devin -p with your prompt, writing the output to a log.