Skip to main content
The schedule command manages scheduled agent execution.

Usage

Commands

Adding Jobs

Options

Examples

Add a daily reminder bound to a specific agent

Add a weekly digest

weekly runs every 7 days (604800 seconds).

Fire-and-forget alert

A reply in #C012345 lands as a brand-new turn instead of resuming the maintenance job’s conversation. Without --no-continuable, a delivered result is continuable by default — a reply resumes the job’s conversation with the brief in context.

Deliver via home channel

Run /sethome in the target chat first.

Deliver into a thread

Append a third :thread_id segment to thread the outbound message — a Slack thread ts, a Telegram forum topic id, or a Discord thread id:
The router preserves the thread segment end-to-end, so the message lands in the Slack thread rooted at message ts 1728987654.001234. Adapters without thread support silently ignore the segment. See Scheduler Delivery → Thread semantics.

Fire-and-forget notice

--no-continuable opts out of session seeding, so a reply starts a fresh session instead of resuming the job. See Continuable Delivery.

Fan-out to all home channels

Deliver back to origin chat

origin requires --channel and --channel-id so the executor can resolve the creating chat.

Blueprints & Suggestions

Create jobs from reusable templates, or accept consent-first suggestions — the same engine that powers the /automations and /blueprint chat commands. See Automation Suggestions for the concepts.

blueprint

Create a schedule from a blueprint template.

blueprint-list

List available blueprints (built-in + user YAML).

suggestions

List pending automation suggestions.

suggestion-accept

Accept a suggestion and create the schedule job.

suggestion-dismiss

Dismiss a suggestion without creating a job.

suggestion-propose

Propose a blueprint as a suggestion (manual/CLI trigger).

Examples

Add with delivery target [Legacy]

Start scheduler

List scheduled jobs

View logs

Stop a job

Delete a job

Skip the model turn when there are no new emails

--pre-run runs scripts/new_mail.sh before each tick. Exit 0 + stdout → agent runs with that stdout appended to the message. Non-zero exit → tick is skipped, no tokens spent, no Telegram ping.
--pre-run is a trusted, human-configured surface — it is not accepted by the agent-callable schedule_add tool, which prevents a prompt-injected agent from persisting arbitrary shell commands on the host. Configure --pre-run only via the CLI, YAML, or Python.

See Also