Skip to main content

scheduler

Registered Go module (internal/modules/scheduler). One agent tool: schedule.

At each cron fire, digitorn-background re-runs this session with an injected user message. The agent keeps accumulated session context. Schedules are durable across restarts.

PropertyValue
Module idscheduler
Version1.0.0
Toolsschedule
Blank-imported bycmd/digitornd

Enable in an app

yaml
tools:
modules:
scheduler: {}
capabilities:
grant:
- module: scheduler

Optional module config (also overridable via env):

FieldDefault / envMeaning
background_urlDIGITORN_BG_URL or http://127.0.0.1:8090Background ops base URL
ops_tokenDIGITORN_BG_OPS_TOKENBearer token for ops
default_replyautoDefault reply when the tool omits it

Tool: schedule

ParamTypeRequiredDescription
schedulestringyes5-field cron: minute hour day-of-month month day-of-week
messagestringyesInstruction injected as the user message each fire
contextstringnoExtra context alongside the message
replystringnoauto, none, or stream
reportsbooleannoDated downloadable folder per run under attachments

Example cron strings: 0 9 * * * (09:00 daily), */15 * * * * (every 15 minutes), 0 9 * * 1-5 (weekdays 09:00).

The handler POSTs to {background_url}/ops/schedules with app_id, session_id, owner, and the params above. On success it returns confirmation and metadata (id, next_run, schedule).

What this is not

ClaimReality
cron_native.schedule / cancel_schedule / remindStub module; those tools do not exist
runtime.scheduler: true aloneSchema field only; does not load this module
One-shot when: "in 5m" / ISO timestamp scheduler API on this toolThis tool is recurring cron + session message only
Watcher loop dependencyNo watch_* tools in Go; unrelated

For app-level channel cron / webhook triggers, see Channels. For HTTP schedule management outside the agent, use the automations / background ops API.