How Scheduling Works
- You define a schedule (cron expression + prompt + config)
- The SDK stores the schedule and manages execution
- At each trigger time a new session is created and the agent is run
- Results are stored, and the CLI can post them to a chat through a connector (Telegram, Slack, and others)
ClineCore. The hub runs as a background process on your machine. It starts automatically when needed and persists schedules across restarts.
Creating Schedules Programmatically with Cline SDK
cline.automation reads schedule files from ~/.cline/cron/, reconciles them, ingests events and lists runs. sdk/examples/cron has sample schedule files.
Schedule Wizard with Cline CLI
If you have the Cline CLI installed (npm i -g cline), run cline schedule to open an interactive menu for creating and managing schedules, browsing execution history, and viewing performance statistics.
Creating Schedules with Flags
--provider and --model.
Managing Schedules
Cron Expression Reference
Use Cases
Daily Standup Summary
Automated Dependency Updates
Codebase Health Report
Concurrency Limits
- Each schedule runs one execution at a time unless you raise
--max-parallel. An execution that comes due while the schedule is busy waits in the queue. - The hub runs at most 10 scheduled executions at once across all schedules.
ClineCore.create({ automation: { globalMaxConcurrency } })changes this limit for the SDK’s own scheduler. - If the hub was stopped when a run was due, it queues one catch-up run when it starts again, not one for each missed time.