Band Band

band cronjobs

The band cronjobs command group manages scheduled recurring tasks. Cron jobs let you run agent tasks on a schedule — for example, running daily code reviews, updating dependencies weekly, or generating reports every morning.

List Cron Jobs

Display all configured cron jobs.

band cronjobs list

Example output:

ID   Project    Schedule       Prompt                           Last Run            Next Run
1    my-app     0 9 * * *     Review open PRs and summar...    2025-12-01 09:00    2025-12-02 09:00
2    my-app     0 0 * * 1     Update npm dependencies          2025-11-25 00:00    2025-12-02 00:00
3    api-server 0 */6 * * *   Run integration test suite       2025-12-01 12:00    2025-12-01 18:00

Create a Cron Job

Schedule a recurring task. The schedule uses standard cron expression syntax (5 fields: minute, hour, day-of-month, month, day-of-week). 

band cronjobs create --project 1 --schedule "0 9 * * *" --prompt "Review all open pull requests and post a summary"

Options:

  • --project <id> — The project ID to run the cron job against (required).
  • --schedule "..." — Cron expression defining the schedule (required).
  • --prompt "..." — The task prompt for the agent (required).

Common Cron Expressions

  • 0 9 * * * — Every day at 9:00 AM
  • 0 0 * * 1 — Every Monday at midnight
  • 0 */6 * * * — Every 6 hours
  • 30 8 * * 1-5 — Weekdays at 8:30 AM
  • 0 0 1 * * — First day of every month at midnight

Update a Cron Job

Modify an existing cron job's schedule or prompt.

band cronjobs update 1 --schedule "30 8 * * 1-5" --prompt "Review open PRs and check CI status"

You can update the schedule, prompt, or both. Fields not provided remain unchanged.

Delete a Cron Job

Remove a cron job. Pending runs are cancelled and the schedule is removed.

band cronjobs delete 2

Trigger a Cron Job

Manually trigger a cron job to run immediately, regardless of its schedule. This is useful for testing or for one-off executions. 

band cronjobs trigger 1

The triggered run creates a new task in a fresh workspace, just like a scheduled run would. It does not affect the next scheduled execution time.

JSON Output

band cronjobs list --output json

Example JSON output:

[
  {'{'}
    "id": 1,
    "projectId": 1,
    "schedule": "0 9 * * *",
    "prompt": "Review open PRs and summarize findings",
    "lastRunAt": "2025-12-01T09:00:00Z",
    "nextRunAt": "2025-12-02T09:00:00Z"
  {'}'}
]