Runs one-time and RFC 5545 recurring Agent tasks in fresh DSH sessions, with visual schedule editing and session-linked history.
Install
# from npm (prebuilt)
dsh plugin --profile web add @alpacachen/dsh-automation
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:alpacachen/dsh-automation
Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).
README
Maintenance status: active maintenance has ended (2026-10-08).
This project will no longer actively develop new features. Compatibility updates for future DSH versions and issue fixes are not promised. The existing code, documentation, and published versions remain available for existing users and reference.
Automation began with a simple idea: let an Agent pick up work at an agreed time, without waiting for us to open a conversation. Scheduling, session continuity, execution records, and message delivery grew out of that idea—and out of the help this project received along the way.
DSH now provides official scheduling capabilities. They are not a complete replacement for this plugin, but for basic scheduling, I would rather pass the baton to the official implementation than keep maintaining a parallel one. New users should first explore the official Schedule / scheduled-task features available in their DSH version.
Thank you to everyone who used the plugin, shared feedback, opened issues, contributed code, or helped test it. Its value was not only in the features we built, but in exploring together how Agents could take part in everyday work.
For existing users:
- Ending maintenance does not immediately disable existing installations, but future DSH upgrades may break compatibility. Validate your setup before relying on it for critical unattended work.
- Tasks, permissions, model and skill settings, execution history, and dsh-im delivery settings do not automatically migrate to the official features. Those features are not guaranteed to cover these capabilities.
- Back up task configuration and run data before migrating. Check the official feature set, validate replacement tasks, and then disable old tasks to avoid duplicate runs. Do not uninstall or delete data before backing it up.
- This change only updates the maintenance notice. It does not archive the repository, deprecate the npm package, delete code, or alter your existing tasks. Forks are welcome under the MIT license.
The original introduction and usage documentation remain below as reference for existing versions, not as a promise of ongoing maintenance.
Thank you for being part of this little project.
Get started
Targets DSH 0.1.7-rc.2 and its current APIs. Older Host versions are not supported.
dsh plugin --profile web add @alpacachen/dsh-automation
Restart dsh web, open a workspace, and make your first request:
Every weekday at 6 PM in Asia/Shanghai, summarize today's changes, next actions, and blockers. Read only; don't change files. Show me the configuration before creating it.
The Agent previews the schedule, permissions, and other settings. It creates the task only after you confirm. Or choose New automation in the sidebar and start from a built-in template.
Plans change: just say “Move the daily handoff to 7 PM.” To receive results in chat, select a bot and saved target under Edit → Message delivery. Set up message delivery ↗
Keep DSH running for scheduled tasks. Runs have a 1-hour limit by default, and interactive approvals are never granted automatically. How execution works →
Demo
Copy an example to your Agent and adjust the time or scope. Every task requires a configuration preview and your confirmation before creation. Fill in missing essentials, such as log paths, before saving the task.
Dependency reviews need working web tools on the Host. For report delivery, configure dsh-im on the same Host, then select and confirm a bot and saved target under Edit → Message delivery; creating the task alone does not enable delivery. Docs maintenance requires write permissions.
Links
More in this category
loopx-project/loopx#dsh-loopx-plugin★ 6305
LoopX, a provider-neutral, local-first state kernel and control plane for long-horizon agents: keeps Goal, Todo, gate, evidence, quota, recovery, and handoff state above DeepSeek Harness, while the plugin bootstraps the CLI and skills, admits bounded same-session continuation, and adds a loopback GoalBar for the exact bound loop.
Q00/ouroboros#integrations/dsh-plugin★ 6223
Config-only bundle that mounts Ouroboros through the DSH MCP client, exposing 36 interview, Seed, execution, evaluation, and evolution workflow tools in DSH.
chuspeeism/dashi-taskboard#deepseek-harness★ 3345
Embeds the active installed Codex Taskboard runtime in the DeepSeek Harness sidebar, using its launcher runtime descriptor instead of a fixed port.
NanmiCoder/dsh-agent-teams★ 2152
AgentTeams multi-agent teams.
EthanYoQ/AI-Novel-Writer#dsh-ai-novel-writer★ 1553
Installs a dedicated AI novel-writing preset and workbench: revisioned local project assets, a compact side drawer, and native approval-gated single-file changes.
tong-io/tongflow#dsh-tongflow★ 1047
TongFlow film-crew studio for image, voice, music and video production: the agent writes per-asset TongFlow workflow files (.tongflow.json) that run through TongFlow plugins, with an embedded workflow canvas, a shot/character/take project layout and a manga-drama template; sessions starting with @tongflow open the Studio view.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.