@moxxy/plugin-scheduler is the engine that fires prompts on a timer. Entries persist in ~/.moxxy/schedules.json; the daemon polls them on an interval and dispatches each due entry into an isolated session.

Add a schedule

# Recurring (5-field cron, IANA timezone optional)
moxxy schedule add weekday-standup \
  --cron "30 8 * * 1-5" \
  --prompt "Draft a standup update from today's git log."

# One-shot at a specific instant
moxxy schedule add follow-up \
  --at "2026-06-01T09:00:00Z" \
  --prompt "Ping me about the migration."

# Hint a channel — the prompt calls the channel's send tool
moxxy schedule add daily-digest \
  --cron "0 9 * * *" \
  --channel telegram \
  --prompt "DM me a summary of unread messages."

Flag	Purpose
--cron "<expr>"	5-field cron expression (min hour dom mon dow).
--at "<iso>"	One-shot ISO-8601 timestamp (or epoch-ms).
--channel <name>	Soft hint — the prompt calls the matching send tool.
--model <id>	Override the active model for this schedule.
--timezone <zone>	IANA zone for cron interpretation (default: system local).

Manage

moxxy schedule list                # everything, with next fire time
moxxy schedule remove <id>
moxxy schedule enable|disable <id>
moxxy schedule run <id>            # fire one immediately (testing)

Daemon

The poller runs in two flavors:

moxxy schedule daemon              # foreground (Ctrl-C stops); fine for ad-hoc tests
moxxy service install scheduler    # launchd / systemd --user — install once, runs forever

moxxy schedule setup is a one-shot helper that installs the daemon and pre-allows the common headless tools (Bash, Read, Glob, etc.) so the agent doesn't deadlock on a permission prompt with no one to answer.

The store, cron evaluator, and poller all live in packages/plugin-scheduler/src/; see cron.ts for the expression parser (supports *, */n, ranges, lists, L).

From inside a turn

The agent can manage schedules itself via these tools:

Tool	Purpose
schedule_create	Add an entry (cron / runAt + prompt).
schedule_list	List with nextFireAt.
schedule_delete	Remove by id.
schedule_enable / schedule_disable	Toggle without deleting.
schedule_run_now	Fire immediately.

Skill-driven schedules

Skills with a schedule: block in their frontmatter are auto-mirrored into the store on startup and after every skill_created event (packages/plugin-scheduler/src/skill-sync.ts). Delete the skill → the schedule disappears on the next sync.

Delivery

Each scheduled run executes in an isolated session — no chat context leaks across firings. Results land in the per-channel inbox dir (default ~/.moxxy/inbox). When --channel telegram is set, the prompt is expected to call telegram_send_message; that's the link to the user.