dsh-automation
Agent 与工作流alpacachen/dsh-automation
在 DeepSeek Harness 中调度和管理一次性与周期性 Agent 任务,可为每个任务选择 Agent、模型、技能与权限,并查看运行记录。
- automation
- coding-agent
- deepseek-harness
- dsh
- dsh-plugin
- rrule
- scheduled-tasks
验证与兼容性
这里展示目录实际采集到的证据;未声明的信息会明确标为未知。
- 当前版本兼容性
- 已在当前目录版本验证
- 声明的 Harness 范围
- 未声明
- 声明的平台
- 未声明
- 适用 Profile
- web
- 构建授权
- 未知
- 权限声明
- 未声明
- 外部服务
- 未声明
- 遥测声明
- 未知
这不是安全背书;安装前仍应查看源码、权限和配置。
查看证据与判定范围
验证仅覆盖标出的来源、版本和 Harness 环境,不代表未来版本仍然兼容。
@alpacachen/dsh-automation@0.3.28- 插件通过清单与静态结构检查,尚未完成运行时加载检查。
README
Thank you, and goodbye
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.