dsh-clock

The built-in reminder system in DeepSeek Harness is session-local: a reminder only lives inside the conversation that asked for it, and a closed conversation keeps its reminders sitting until somebody reopens it. That means you cannot tell a long-running task "come back to this at 09:00" and then close the tab. dsh-clock fills exactly that gap. It lifts alarms out of a single conversation: you pick an instant, a keyword, and any target conversation, and when that instant passes the keyword is delivered into the target even if it is already closed.

Every wake carries a full time ledger: the scheduled instant, the actual delivery instant, the signed drift, and an explicit warning whenever the delivery is late. A wake that arrives three hours overdue does not read like one that arrived on time. Under the hood, three trigger layers guard the same delivery—an in-process timer that holds a single setTimeout for the earliest pending alarm, a Windows scheduled task with StartWhenAvailable that catches sleep and suspension, and a replay-at-startup pass that recovers alarms missed while the host was down. All three converge on one claim-then-deliver path; whichever wins, the others find nothing to claim, so stacking three triggers cannot deliver one wake three times. The panel provides a calendar view, separate scrollable pending and settled lists, branch awareness that asks whether to copy alarms onto a forked conversation, and immediate fire or cancel, all with idempotent guarantees.

It is built for people running multi-step, time-horizon agent workflows inside DeepSeek Harness: you need a task to be woken at a specific moment without babysitting a conversation window, or you want the agent itself to create and manage alarms via a tool and a bundled skill that conveys the subtleties a single line of advertisement cannot. One-shot, cross-session, timestamped wakes: that is the only thing this plugin does, and it does it with three layers of timing assurance.