dsh-task-dispatch-table
定时任务调度器：一个 dsh 主机插件，通过单个任务表驱动周期性代理任务，并将每次运行作为独立的 dsh 会话进行调度（调度本身不调用模型）
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-task-dispatch-table@0.1.11
Task Dispatch Table 以 dsh-task-dispatch-table 发布，当前版本为 0.1.11。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English | 中文
One dsh host plugin: a single table of task definitions drives your recurring agent work — when a task is due, it is dispatched as an independent dsh session that an agent actually executes. The scheduling itself is pure program logic and never burns a token.
Task list with a task expanded
dsh plugin --profile web add dsh-task-dispatch-table
Every release is published to npm, so it works right after installing — no extra configuration and no local build. The UI copy is bilingual and follows dsh's interface language (Settings → General → Language).
The plugin keeps two layers of state:
| Object | What it is | What it decides |
|---|---|---|
| Task definition | One row per scheduled unit: title, prompt, schedule, attachments, workspace, model, dependencies, on/off switch | Whether and how a task should run |
| Task instance | One row per actual run: status, planned/actual time, session id, token usage, artifacts | What happened in a run |
The scheduler is a plain loop: on every tick it computes which tasks are due, claims them atomically in SQLite, dispatches each as a new dsh session in the task's workspace, then tracks the session via a receipt tool the session is required to call when done. Missed slots (host was down past the allowed delay) are recorded and marked skipped instead of disappearing.
The task editor as a right-hand split panel
Press New task (or Edit on a card) and the editor opens as a layout split panel, not a floating drawer: basics, schedule, prompt (with version history), advanced options, attachments and upstream tasks. Attachments are either links to files already in the workspace or uploads (stored in the task's own directory, up to 20 MB each).
The footer switches between View / Edit modes: View is a read-only rendering of the task — configuration, last run, and the prompt — for checking a task without risking an accidental edit.
Recurring schedule: daily at 18:12 with an allowed delay
Three modes, each showing a plain-language preview of the next run:
Every mode has an allowed delay: if the host was busy or down when the moment came, the run still fires within the window; past the window the slot is recorded as skipped (with the reason) rather than lost silently. A task card's Run now button triggers an extra run immediately, outside the schedule.
Upstream tasks declared in the editor
A task declares which upstream tasks must have succeeded before it may run (the Airflow / GitHub Actions needs model — the downstream declares, so adding a downstream never touches the upstream). When the task fires, the plugin freezes which upstream instance it matched together with that instance's outputs and passes them into the new session, so the downstream agent reads exactly the data its run was keyed to — even if the upstream has re-run since.
A task expanded: runs table with status, times, token usage and artifacts
Expanding a task opens three panels: basic info (configuration side by side with the last run), runs (one row per instance: status, planned vs actual time, duration, token usage, artifacts, and a button to open the archived session), and logs (the plugin's own diagnostic log for that task — missed slots, missing attachments, manual runs).
View session opens the archived run as a read-only record: the files the session received from upstream tasks (frozen at dispatch time), the task's attachments, the dispatch request with its timing and token usage — and a continue conversation button that forks the archived session into a new interactive one.
The cross-task execution timeline, one entry expanded
The Records tab is the ledger across all tasks, grouped by day and filtered by time range, workspace, status and task. Each entry expands in place to its full artifact list and raw event log (state changes, dispatch record, receipt); the archived session itself opens only when you press View session.
Monthly calendar with actual runs as filled dots and planned runs as dashed dots
The Schedule tab is a month view. Days show two kinds of markers: actual runs from the instance table (solid dots in status colors) and planned runs computed from the current task definitions (dashed dots). Clicking a day expands that week in place with the full run details — the same entry blocks as the timeline, expandable again down to artifacts and events.
Settings page: plugin settings on top, plugin log below
The Settings tab is the primary place to configure the plugin. Each item shows whether it was customized and can be reset individually; changes are staged and written only on Save; the log block below shows the plugin's diagnostic log with level coloring and auto-refresh.
| Item | Default | Meaning |
|---|---|---|
| Tick interval | 60 s | How often the scheduler scans the task table |
| Run log retention | 30 days | How long diagnostic log rows are kept |
| Temp attachment retention | 7 days | How long uploaded temp files are kept |
| Default model | follow host | Model used when a task does not pick one |
| Dispatch grace | 60 s | Max wait for a dispatched session to appear |
| Run lease | 1800 s | How long a silent session keeps its lease before being reclaimed |
| Observation window | 300 s | How long an unknown-status session is watched before being judged dead |
Configuration is stored in the plugin's own state database, so it survives host config resets; defaults apply underneath.
npm install
npm run build # builds host first, then client
npm run typecheck
npm run smoke # smoke tests against dist/
dist/is a build artefact committed to git — dsh installs plugins from git/npm without running build scripts, so after changingsrc/you must runnpm run buildand commitdist/with it, or the change will not take effect.
MIT © 2026 cq-guojia