* feat(schedule): manage Host tasks with typed timing and delivery targets * fix(schedule): align task creation button halves * refactor(schedule): remove obsolete Session reminder runtime * refactor(schedule): simplify task UI and preserve keyboard navigation * fix(schedule): address task delivery and interface review findings * test(schedule): normalize bundle module paths on Windows * fix(schedule): cover reserved targets and trim unrelated changes * refactor(schedule): minimize task management changes after rebase * test(schedule): align rebased fixtures and documentation records * test(schedule): refresh SDK scenarios added on master --------- Co-authored-by: Magolor <[email protected]>
4.0 KiB
4.0 KiB
kind, description
| kind | description |
|---|---|
| upgrade-guide | The Schedule model tools become `schedule_create`, `schedule_list`, `schedule_view`, and `schedule_edit` over every Host task, and `schedule_update` and `schedule_delete` are removed. |
Schedule tools manage every Host task by RRULE and target
English | 中文
Change
Earlier, @deepseek-ai/dsh-tool-schedule registered schedule_create, schedule_list, schedule_update, and schedule_delete. They managed only the reminders of the calling Session, and schedule_create took one timing selector: after_seconds, at, every_seconds, daily, weekly, or cron.
The package now registers schedule_create, schedule_list, schedule_view, and schedule_edit:
schedule_createtakestitle,prompt,rrule(oneDTSTARTline and oneRRULEline), andtarget(this_session,new_once, ornew). It accepts no timing selector.schedule_listreturns one page{ items, shown, total, limit, offset }of active, paused, and ended tasks instead of an array of active reminders.schedule_viewreads one task by id.schedule_editwithaction: "update"replacesschedule_updateand can also changerruleandtargetor pause and resume a task;action: "delete"replacesschedule_delete.- Each tool reads, changes, and deletes any Host task by id, not only the tasks of the calling Session.
- A call from a delegated subagent returns
subagent_sessionwith the messageA delegated subagent cannot use scheduled tasks.
Existing reminders keep their timing and delivery. Recorded Sessions keep their earlier calls and results, and the Web transcript still renders them.
This affects:
- prompts, skills, and scripts that tell a model to call
schedule_update,schedule_delete, or a timing selector; - deployments that rely on each Session seeing only its own reminders;
- TypeScript code that imports
scheduleViewfrom the root entry, orScheduleView,ScheduleState,ScheduleDeliveryMode,ScheduleCreateValue,ScheduleListValue,ScheduleDeleteRequest,ScheduleDeleteValue,ScheduleTimingChange,ScheduleUpdateContent,ScheduleUpdateMiss,ScheduleUpdateRequest,ScheduleUpdateResult, orScheduleUpdateValuefrom the root or/cliententry of@deepseek-ai/dsh-schedule.
Migration
- In prompts, skills, and scripts, replace
schedule_updateandschedule_deletewithschedule_edit, replace each timing selector with an RRULE, and supply the requiredtargeton creation. For example,daily: { time: "09:00:00", time_zone: "Asia/Shanghai" }becomesrrule: "DTSTART;TZID=Asia/Shanghai:20261013T090000\nRRULE:FREQ=DAILY"; usetarget: "this_session"to keep delivery in the calling Session. - If the agents of a preset must not manage the tasks of other Sessions, remove the
@deepseek-ai/dsh-tool-schedulerow from that preset. - In TypeScript code, use
ScheduleCreateRequest,ScheduleTiming,SchedulePatch, andScheduleEditRequestfor writes, andScheduleViewResult,ScheduleListResult, andScheduleEditResultfor reads and edits. CallScheduleService.view, pagedlist, andeditinstead ofscheduleView,update, anddelete.ScheduleDeleteResult,ScheduleDeleteChange, andScheduleDeleteInactiveResultremain exported from the root and/client; the old request/value types above do not. The Schedule service README describes these APIs. - Custom compositions must provide both
toolsandsystemPromptbefore mounting this consumer; registration also waits forschedule. Thetool:schedulesection supplies the shared authorization instruction. Acomplete: trueprompt override must include that instruction itself. - Open a Session under each changed preset and confirm that its tool list shows the four tool names. Delegate a task and confirm that a Schedule tool call from the child returns
subagent_session; the child's tool list includes the four names, as Configure subagent composition through presets describes.