dsh-tui-cron

Running long-lived agent sessions in dsh-TUI often means you want periodic follow-ups without babysitting the terminal: inject a checklist prompt every few hours, drop a reminder at midnight, or append a fixed cadence of instructions. dsh-tui-cron turns that need into a single five-field cron expression paired with a prompt string.

The workflow is simple. You save a schedule via /cron using standard five-field cron syntax (wildcards, step values, ranges, comma lists, Sunday as 0 or 7, Vixie OR-semantics for day/weekday). When the slot fires, the prompt is injected into the live conversation as a follow-up user message. A running turn is never interrupted; the message simply queues as the next turn. The panel UI supports arrow-key navigation, Space to toggle, double-press d to delete, and data lives in a plain local JSON file you can inspect or edit by hand.

One important caveat: the scheduler is bound to the lifetime of the current dsh profile process. Next-fire times are computed from the moment of startup, so any slots missed while the TUI was offline are never retroactively triggered. It is best suited for developers who keep dsh-TUI open as a persistent workbench and want lightweight, in-process cadence control without spinning up a system cron daemon. If you need a global, cross-session scheduler, look elsewhere; as a per-session rhythm tool, it is deliberately small, transparent, and out of the way.