⏱️ dsh-automation

Run coding tasks on schedule. Manage them from Web or Agent.

<br> <tr><td align="left">

🕒  Need recurring or one-shot coding work to run later without relying on an old chat?<br> 🧭  Need each unattended run to stay inside an explicit workspace and permission boundary?<br> 🧾  Need to inspect what ran, which revision it used, and how it ended?

</td></tr>

✨ dsh-automation turns all three requirements into one workflow.

Create and manage schedules from DSH Web or any eligible root Agent. Every dispatched occurrence starts in a fresh root Agent and Session, then leaves an auditable record.

Self-contained task + schedule + permission boundary → fresh root Agent + fresh Session + durable run history

<br>

Why automation · Features · Install · Quick start · Safety · Technical details

English · 简体中文

<br>

---

<a id="why-automation"></a>

🎯 Why automation

DSH Core Schedule is the right tool for reminders in the current conversation: “come back to this Session in ten minutes.” dsh-automation handles a different job: “run this complete task independently every weekday and leave me a result I can inspect.”

	DSH Core Schedule	dsh-automation
Execution context	Returns to the same live Agent	Starts a fresh root Agent and Session
Input	A follow-up inside existing context	A saved, self-contained task
Scope	Current Session Log	One canonical DSH workspace
History	Conversation events	Definition revisions and durable run records
Best for	Reminders and same-chat follow-ups	Repeated or one-shot standalone coding work

If a task depends on unstated chat history, needs an interactive approval halfway through, or should react to a file, HTTP, or process condition rather than time, it is not a good automation yet.

---

<a id="features"></a>

✨ Features

🕹️ One control plane, two ways in

• DSH Web: open Automations from the sidebar or the conversation tab to create a rule, pause or resume it, run it now, delete it, and inspect recent runs. On the blank New Session screen, the sidebar shortcut tells you to start a conversation instead of failing silently.
• Any eligible root Agent: ask in natural language. Six scoped tools let the Agent manage automations only for its exact workspace.

There is no separate bot, daemon UI, or third-party scheduler to operate.

📅 Schedules people can read

Create a one-shot, fixed-interval, daily, or weekly rule. Daily and weekly schedules use an IANA time zone; the friendly form is normalized into a validated RFC 5545 RRULE for persistence and inspection.

🧠 A model target for each automation

The Web form can follow the live global model or pin one provider/model pair. A pinned model can use its own default reasoning effort or one of the opaque effort values advertised by that exact model. The card shows the saved target, and each run keeps the same target in its immutable snapshot.

…