Who it is forA developer using dsh during the workday who wants routine agent jobs to run later at lower off-peak prices.
The problemAgent work takes your attention while you wait, and it often runs at peak prices when you are busy.
The outcomeTasks run unattended inside the off-peak window, and you review the results and spend the next day.
What you need first
- DeepSeek Harness (dsh) installed
- The lowtide plugin installed into dsh
- A model connected to your Harness
- A workspace directory for the project the tasks will touch
Steps
- Open the new-task modal in dsh with lowtide installed and pick a strategy such as single or iterative.
- Set rounds, priority, and run mode for the task, then file it so it lands as pending review.
- Release each task you trust, or in batch mode release the whole batch from the gate card 30 minutes before the window.
- Let the queued tasks run when the off-peak window opens.
- Open the execution report in the morning, retry failed tasks, and merge the good results.
Prompt for your agent
Using the lowtide plugin in DeepSeek Harness, queue the task described here for <target project path> with the single strategy and release it for the next off-peak window. Expected output: a task in the queue with status queued, then an execution report listing results and actual spend. Verify that the task appears in the report with its workspace and cost.
Caveat. The README says the batch runs in DeepSeek's valley hours, so the savings depend on DeepSeek's published peak and valley times, and non-official models show price unknown in the ledger.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for KelaoHu/dsh-lowtide and "Queue daytime tasks and collect results at off-peak"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer