Introduction

In the DSH plugin ecosystem, scheduled triggers usually require converting scheduled events at the scheduled time into subsequent executable session Runs. dsh-cron addresses this problem: it provides persistent calendar triggers for DSH Automation, converting one-time or recurring schedules into idempotent new session Runs, but does not execute Agent turns itself.

What is this

omdsh-dev/dsh-cron is a DSH plugin under the MIT license, positioned as a persistent calendar trigger for DSH Automation.

It handles schedule parsing, timezone calculation, persistent occurrence records, idempotent submission, and the Task Center UI, and depends on the dsh-automation public service contract.

Core Capabilities

The verified plugin capabilities are introduced below:

  • Supports 5-minute field cron.
  • Supports one-time RFC 3339 at timestamps.
  • Supports IANA timezones and daylight-saving-aware occurrence calculation.
  • Generates persistent records and idempotent submissions for each scheduled occurrence.
  • Missed recurring tasks use “latest-only catch-up” (no replay of older backlog).
  • Provides a browser Task Center via the dsh.client manifest.
  • Supports tools, commands, and RPC for headless profiles.
  • Provides model tools cron_add, cron_update, cron_list, cron_remove.
  • Provides the /cron command for adding, one-time adding, pausing, resuming, and deleting tasks.
  • Depends on the dsh-automation public service contract.

Installation and Activation

This plugin requires the dsh-automation >=0.2.0-alpha.0 <0.3.0 service contract. The installation command is as follows:

dsh plugin --profile web add github:omdsh-dev/dsh-cron

After installation, the plugin can provide a browser Task Center via the dsh.client manifest and be used via tools, commands, and RPC in headless profiles.

Typical Usage

Model Tools

dsh-cron provides the following model tools:

  1. cron_add: Create recurring or one-time tasks.
  2. cron_update: Pause or resume tasks.
  3. cron_list: View schedules, occurrences, linked Runs, and outcomes.
  4. cron_remove: Delete tasks.

The /cron Command

Tasks can be managed using the /cron command. Examples are as follows:

/cron add 0 9 * * 1-5 Summarize the project status
/cron add tz=Asia/Shanghai 30 18 * * 5 Prepare the weekly report
/cron add-at 2026-09-01T09:00:00+08:00 Run the release checklist
/cron pause cron-1
/cron resume cron-1
/cron remove cron-1

These commands are used to add recurring tasks, add one-time tasks, pause tasks, resume tasks, and delete tasks, respectively.

Applicable Scenarios and Notes

Suitable for DSH workflows that need to convert calendar schedules into DSH Automation Runs, especially for recurring schedules, one-time schedules, cross-timezone schedules, and headless management scenarios.

Usage Notes:

  • The plugin runs with the current dsh process permissions; check the source code and license before installing.
  • This plugin requires the dsh-automation >=0.2.0-alpha.0 <0.3.0 service contract.
  • The plugin itself does not execute Agent turns.
  • Missed recurring tasks only catch up with the latest one; older backlogs are not replayed.
  • Pausing preserves the schedule; resuming will cause recurring schedules to skip occurrences before the current time.
  • Browser/API tasks must send cwd or inherit defaultCwd.
  • Legacy tasks without cwd or defaultCwd will be safely paused and marked with migrationIssue.
  • Does not import private dsh-automation source code, nor does it require modifying deepseek-harness.

Links

  • Directory Page: https://www.skillhub.cn/plugins/omdsh-dev/dsh-cron
  • GitHub: https://github.com/omdsh-dev/dsh-cron