Agent Scheduler: Run AI Tasks on a Schedule

The SuperBuilder Scheduler lets you set AI agent tasks to run automatically at any time — on a recurring schedule or as a one-shot future job. Write the task once, set the schedule, and let it run.

What You Can Schedule

Almost anything you'd run manually in SuperBuilder can be scheduled:

• Nightly test runs with automatic failure fixes
• Weekly dependency update checks
• Daily code review summaries sent to your team
• Recurring documentation refreshes
• Periodic database cleanup and optimization tasks
• End-of-sprint changelog generation

If it's a task you find yourself doing on a regular cadence, it belongs in the scheduler.

How to Create a Scheduled Task

1. In any SuperBuilder thread, write your task prompt
2. Instead of running it immediately, click Schedule
3. Set the schedule: one-time datetime, or a recurring cron expression
4. Optionally configure the workspace, model, and notification preferences
5. Save — the task is now scheduled and will run automatically

You can create scheduled tasks from anywhere in SuperBuilder — from an existing thread, from the scheduler panel, or from the command palette.

Cron Scheduling

For recurring tasks, SuperBuilder uses standard cron expressions:

• 0 2 * * * — every night at 2 AM
• 0 9 * * 1 — every Monday morning at 9 AM
• 0 */4 * * * — every 4 hours
• 0 0 1 * * — first of every month at midnight

You can also use plain-English shortcuts:

• Daily — runs at the same time every day
• Weekly — same day and time every week
• Monthly — same date and time every month

The scheduler shows you a human-readable interpretation of your cron expression so you can confirm it's doing what you expect before saving.

Viewing Scheduled Tasks

The Scheduler panel shows all your scheduled tasks:

• Upcoming runs — tasks scheduled to run next, with countdowns
• Run history — past runs with output, duration, and cost
• Status — whether a task is active, paused, or had an error on its last run
• Edit / Pause / Delete — manage any scheduled task from the panel

You can expand any past run to see the full agent output — what it changed, what commands it ran, and the complete conversation log.

Notifications

When a scheduled task finishes, SuperBuilder notifies you:

• Thread done — a notification appears with a summary of what was completed
• Needs attention — if the task encountered something it couldn't resolve alone, it flags it for your review
• Error — if something went wrong (rate limit, API error, task failure), you're notified with context

You can configure notifications per scheduled task. Some things you want to know about immediately; others you only care about if they fail.

Practical Examples

Nightly dependency check

"Check for outdated npm packages in this repo. If any have security advisories, update them and run the test suite. If tests pass, commit the changes. If tests fail, create a new thread with the failures."

Runs every night. You wake up to either clean updates or a clear report of what needs human attention.

Weekly changelog

"Look at all commits merged to main in the last 7 days. Write a changelog entry summarizing user-facing changes, grouped by feature area. Append it to CHANGELOG.md and commit."

Runs every Monday. Your CHANGELOG stays current without anyone having to do it manually.

Recurring code review

"Review the last 3 pull requests merged this week. For each one, write a brief quality assessment: what was done well, what could be improved, and any patterns worth discussing in the next retro."

Runs every Friday. Gives your team something concrete to discuss without the overhead of formal reviews.

Combining Scheduler with Smart Queue

Long-running scheduled tasks work with the Smart Queue automatically. If a scheduled task involves many sub-tasks (e.g., "fix all lint errors in the repo"), the queue manages rate limits through the entire run without intervention.

One-Shot Scheduling

Not everything is recurring. You can schedule a task to run once at a specific time:

• "Run this migration task at 3 AM Saturday when traffic is low"
• "Do this refactor during the deploy window on Thursday"
• "Run this analysis job tonight and send me the results in the morning"

One-shot tasks work exactly like recurring ones — they just don't repeat after running.

Frequently Asked Questions

Does the scheduler work when my Mac is closed?

For cloud-routed tasks, yes — the scheduler runs on SuperBuilder's infrastructure, not on your device. For tasks that require local execution, SuperBuilder will queue them to run when your device is next online.

Can I test a scheduled task before it runs?

Yes. Any scheduled task has a "Run now" button that triggers it immediately as a test run. The test run appears in the history alongside scheduled runs.

What time zone does the scheduler use?

Scheduled tasks use your local time zone by default. You can configure a specific time zone per task.

Can I share scheduled tasks with teammates?

Scheduled tasks are per-workspace. Workspace members can see, edit, and manage shared scheduled tasks.

How far in advance can I schedule?

There's no limit. You can schedule a task a year from now if you want.