Schedules from the CLI
clisbot schedule creates and manages new-agent schedules from your terminal, useful for headless boxes and scripts. Every run starts a fresh agent.
Run workspaces are archived when each run ends by default. The CLI has no Archive on finish flag; change the option in the app to keep subsequent run workspaces active.
Create
Without --mode, the command fails and lists the provider's modes.
Overnight refactor on Codex:
clisbot schedule create \
--every 30m \
--name overnight-refactor \
--provider codex/gpt-5.5 \
--mode auto-review \
--cwd ~/dev/my-app \
--max-runs 16 \
--expires-in 10h \
"Continue the refactor. Run the focused checks. Leave a short status note."
Long build babysitter on Claude:
clisbot schedule create \
--every 5m \
--name build-watch \
--provider claude/opus-4.7 \
--mode auto \
--cwd ~/dev/my-app \
--max-runs 24 \
"Check the release build. If it failed, inspect logs, fix the cause, and rerun."
Daily GitHub triage on GLM through OpenCode:
clisbot schedule create \
--cron "0 14 * * 1-5" \
--timezone UTC \
--run-now \
--name github-triage \
--provider opencode/openrouter/glm-5.1 \
--mode build \
--cwd ~/dev/my-app \
"Triage GitHub issues, PRs, and failing checks. Summarize what needs attention."
Morning triage at 9 AM in New York, including daylight saving time changes:
clisbot schedule create \
--cron "0 9 * * 1-5" \
--timezone America/New_York \
--name morning-triage \
--provider codex/gpt-5.5 \
--mode auto-review \
--cwd ~/dev/my-app \
"Review overnight CI failures and summarize anything urgent."
Heartbeats
Inside a running Clisbot agent, create a heartbeat for that same conversation:
clisbot heartbeat create \
--cron "*/20 * * * *" \
--max-runs 12 \
--name heartbeat \
"Check the current task state and continue with the next useful step."
The heartbeat interface is deliberately small:
clisbot heartbeat update <id> --cron "*/10 * * * *" --max-runs 6
clisbot heartbeat delete <id>
Updating a heartbeat changes its cron cadence, optional time zone, and Max runs. Its target and prompt stay fixed. Heartbeat commands require CLISBOT_AGENT_ID, which Clisbot sets inside agent sessions.
Heartbeats require a raw --cron expression. The --every presets below are available only for new-agent schedules.
Manage
clisbot schedule ls
clisbot schedule inspect <id>
clisbot schedule logs <id>
clisbot schedule pause <id>
clisbot schedule resume <id>
clisbot schedule run-once <id>
clisbot schedule update <id> --every 10m --max-runs 6
clisbot schedule delete <id>
Cadence
Use --cron "<expr>" for a 5-field cron expression. For common cron-compatible cadences, --every <duration> accepts presets such as 5m or 1h and compiles them to cron. It does not create a rolling interval anchored to creation time.
Schedules default to UTC. Pass --timezone <IANA> to interpret cron fields in a local wall-clock time zone, for example --timezone America/New_York. The persisted nextRunAt is still a UTC instant, but it is computed from that local time zone so recurring jobs stay at the same local time across daylight saving time changes.
A schedule or heartbeat that repeats more than once a day needs --max-runs, so a short cadence never runs without end. Every N minutes, hourly, and 0 9,17 * * * all count; a daily or weekly time does not. Max runs counts every run since the schedule was created.
Schedules wait for the next matching cron time by default. Pass --run-now to start one immediate run on creation.
Start the command with clisbot --host <target> schedule create ... when targeting a remote daemon. Pass --cwd; your local working directory may not exist on the remote machine.