Skip to content

Releases: catsenior507/dsh-clock

v0.1.0 ??calendar and clock with cross-session wake

Choose a tag to compare

@catsenior507 catsenior507 released this 11 Sep 10:48

First public release of the calendar and clock plugin for DeepSeek Harness.

What it does

Set an instant, a keyword, and the conversation to wake. When the instant passes the keyword is delivered
into that conversation ??even if it is closed, because delivery goes through the session controller,
which resumes an ordinary session before appending.

Every wake carries the clock

The scheduled instant, the actual instant, the signed drift, and an explicit warning when it is late. A wake
that arrives overdue must not read like one that arrived on time.

Timing: three layers over one delivery path

  • An in-process timer armed for the earliest pending alarm ??one setTimeout, re-derived on change, never a polling loop.
  • A Windows scheduled task mirroring that instant, with StartWhenAvailable so the OS catches up after sleep or a missed schedule.
  • A replay at host start, which is what actually delivers an alarm whose instant passed while the host was down.

All three claim before they deliver, so stacking them cannot deliver one wake twice.

In this release

  • Calendar and clock panel: month grid, live countdown, alarm rows with fire / cancel / delete.
  • An agent-facing clock tool: now, set, list, cancel.
  • 26 unit tests.

Install

npm install
npm run build
dsh plugin --profile web add <path-or-git-url>

Limits, stated plainly

A wake needs a running host ??only the host can resume a session. If dsh web is not running at the scheduled
instant the alarm is delivered as soon as it is, and the message says how late it is. It is not a push
notification. One-shot alarms only; no recurrence rules yet.