titanwings/dsh-automation
DSH Automation Plug-in: Let Coding tasks run as scheduled in a new Agent Session, and schedule tasks can be created and managed by users or Agents
dsh-automation lets you schedule and automate coding tasks directly inside DSH. Each scheduled or one-shot task starts a fresh root Agent and Session with an explicit workspace and permission boundary, then leaves an auditable run record. Create and manage schedules from the DSH Web UI or any eligible root Agent. Think cron-for-your-codebase — no external task runner or CI pipeline required.
Install
dsh plugin --profile web add github:titanwings/dsh-automation#v0.1.7Version tag keeps the install reproducible (README pin refreshed from v0.1.6 to v0.1.7 on 2026-09-18). If you run DSH from source, use pnpm dsh in place of dsh. Restart the profile after install. Re-verified 2026-09-18: README install line now pins #v0.1.7 (entry had #v0.1.6).
Compatibility
Node.js 22.19+. DSH web profile. Verdict: incompatible with latest DSH rc — check releases for updated compat.
Details
- Repo: titanwings/dsh-automation
- Category: Agent Capabilities
- Stars: 69
- Version: 0.1.7 (README pin, re-verified 2026-09-18)
- Last push: 2026-09-08
- First seen: 2026-08-13
Recent updates
v0.1.6: current stable. Ships built Host and Web bundles; git install runs no build step.
FAQ
- What kinds of tasks can I automate?
- Any DSH coding task: recurring code checks, one-shot delayed runs, nightly refactors, scheduled test runs. Each run is isolated in a fresh Agent/Session.
- How does permission bounding work?
- Each dispatched occurrence stays inside an explicit workspace and permission boundary you set when creating the schedule — the automation can't exceed your defined scope.
- Where do I see run history?
- Each run leaves an auditable record viewable from the DSH Web UI or by inspecting the run log directly.
Alternatives
SepineTam/mcp-for-stata · omdsh-dev/dsh_workflow