Every engineering team has a quiet backlog of things that should happen on schedule, but often slip – like weekly release notes, feature flag cleanups, and onboarding QA sweeps. None of these tasks are difficult, but they slip through the cracks precisely because no single instance feels urgent enough to prioritize.
Starting today, Devin can schedule its own sessions to take care of work like this. You simply describe what should happen on a recurring basis, and Devin figures out the cadence, sets up the schedule, and runs it automatically going forward. There's no cron job to configure and no workflow builder to learn; instead, you're just telling Devin what you need done, the same way you would for any other task, and Devin takes ownership of making sure it keeps happening.
The most natural way into this feature is to let Devin do something once and then tell it to keep doing it.
For example: you might ask Devin to audit your feature flags, and find anything that's been at full rollout for more than two weeks. Devin opens a PR to remove the flag and pings the owner. The results are exactly what you wanted, and it occurs to you that this is the kind of thing that should just happen every Monday morning.
Now, you can simply tell Devin: "Schedule this for every Monday at 9am." Devin will set up a schedule to wake up each Monday at 9am and run the same workflow, so you can stop thinking about it. One good session can save you time every day, week, or month on recurring tasks to support your work.
One feature that makes this meaningfully different from a scheduled script is that Devin carries state between runs. It reads and writes its own notes across sessions, which means each run builds on the context of the one before it rather than starting from scratch.
This matters most for tasks that accumulate over time. If you set up a Devin to compile release notes every Friday, it won't re-summarize the PRs it already covered last week, because Devin knows where it left off, picks up from there, and gives you a clean summary of just what's new. If you have a Devin watching your #feature-requests channel every morning, it tracks which messages it's already processed, notices when themes recur, and surfaces only what's changed since yesterday. The longer a scheduled Devin runs, the more useful its output becomes, because it's building on a growing body of its own context rather than treating every run as an isolated event.
Earlier this week we launched Managed Devins, which let Devin break large tasks into pieces and delegate them to parallel agents, each running in their own isolated VM. Scheduled Devins and Managed Devins compose naturally together.
That means you can set up a weekly QA pass where Devin spins up a managed Devin for each page of your application, tests them all in parallel, compiles the results into a single report, and posts it to your team's Slack channel — automatically, every Friday afternoon, without anyone needing to kick it off. The combination of parallel execution and recurring scheduling is where this starts to feel less like a developer tool and more like a member of the team that just handles things.
Here are a few examples of the kinds of recurring work that Scheduled Devins handle well. Click any prompt to open it directly in Devin.