1.9 KiB
Session-local Schedule
English | 中文
This overlay opts one dsh web process into Schedule reminders without changing the shipped default Web composition:
dsh web --patch examples/web-schedule/cordis.yml
The current overlay supports one-shot reminders created with a positive whole-number after_seconds or an absolute at target. The model manages them through schedule_create, schedule_list, and schedule_delete; every result identifies delivery as session-local.
The browser attaches its IANA zone to each prompt. Time-context tells the model to interpret otherwise-unqualified dates and times in that request's browser zone. This assumption belongs to natural-language interpretation only: schedule_create.at must be either a strict RFC 3339 date-time with Z or a numeric offset, or { date, time, time_zone } with an explicit UTC or IANA Area/Location zone. Schedule does not retain or infer a Session default zone. Daylight-saving gaps are rejected, overlaps choose the first instant, and successful records keep only the resulting UTC target.
The original Session log owns each reminder. A live root Agent waits until it is fully idle, then queues a normal follow-up turn in that conversation. It never steers current work and adds no separate receipt or reminder card. Closing the process or leaving the Session cold stops its in-memory timer without deleting the record; reopening that same Session restores the wait and delivers an overdue reminder. Reading cold history never activates it, and a fork does not inherit its parent's reminders.
Create and actual delete operations acknowledge success only after Session persistence confirms their event prefix. Schedule does not provide browser, operating-system, email, SMS, or other external notification. A durable dispatch records that the follow-up was queued; it does not acknowledge model success or user receipt.
Fixed-rate and cron rules are not supported by this version.