v1.20.60see what's new →

Schedule agents

Recurring background work on a cron, plus one-shot runs scheduled at a wall-clock time. The scheduler auto-starts the first time you add a routine — no daemon to babysit.

Recurring (cron)

agents routines add standup \
    --schedule "0 9 * * 1-5" \
    --agent claude \
    --prompt "Draft a standup from yesterday's git log"

Standard 5-field cron expressions. The routine runs in the background under the same auth and resource layers as an interactive agents run — skills, MCP servers, secrets, and pinned versions all apply.

One-shot

agents routines add deploy-check \
    --at "14:30" \
    --agent codex \
    --prompt "Verify the staging deploy at https://staging.example.com"

Use --at "14:30" for a single run today, or a full ISO timestamp for a future date. Once it fires, the routine is removed.

Manage

agents routines list           # see what's scheduled
agents routines run standup    # fire it now, out of cycle
agents routines logs standup   # tail the last run
agents routines remove standup

Options

Use --timezone to interpret cron and one-shot times in a named timezone, --timeout to cap runtime, --end-at to auto-disable after an ISO timestamp, and --workflow to run an installed workflow instead of a direct agent prompt.

Routines also support --mode, --effort, and --disabled at creation time. Secrets still attach at the agent run layer; create or manage bundles from Secrets.

Related: Hooks, Secrets, Sessions.