dsh-peak-valley-queue

DeepSeek charges a premium for API calls made during peak windows compared to off-peak (valley) windows, and much of the typical workload—bulk rewriting, summarization batches, inspection checklists, recurring report generation—does not need an instant response. dsh-peak-valley-queue closes that timing gap with a single switch beside the composer: when toggled on, every outgoing message is intercepted into a FIFO task queue instead of being sent directly, and the queue auto-dispatches in order once a valley window opens and sufficient lead time remains before the next peak, all without manual intervention.

Core capabilities include fully configurable peak/valley schedules (overlapping ranges, weekend policies, timezone choice, with DeepSeek's official schedule as default); precise four-state completion detection (completed, aborted, failed, blocked) backed by redundant signals—a turn/end reason, agent idle status, a 10-second watchdog, and client-side polling—so no single missed event can wedge a task in the running state; automatic queue pause with a browser system notification (repeated every 30 minutes, plus an optional custom reminder command) on failure or interruption, resuming only when you explicitly click Continue to prevent silent infinite retries; per-session isolated, persistent queues written to the local DSH data directory and never touching workspace files; and integration with dsh-todo-enhancer, which flips a task to a pending-confirmation state and halts the queue when decision-list markers appear in a reply, waiting for you to resolve each item before proceeding.

This plugin is best suited to heavy DeepSeek users whose workflows skew toward batch, deferrable tasks and who want to anchor API spend to off-peak rates. If your use case demands real-time conversation, urgent delivery during peak windows, step-by-step interactive debugging where you need to see each model response before deciding the next move, or tasks that depend on immediate human confirmation, the queuing delay is counterproductive—simply leave the switch off to restore direct sending. The two modes coexist without conflict.