**标求助：DSH 定时任务如何实现 WorkBuddy 式“独立会话”模式？81 个任务挤在一个对话里已无法管理**

[shadapang]

中文版

之前用 WorkBuddy，建定时任务就是对话里说一句，任务直接挂到独立的自动化列表里，每次执行拉起独立会话，跟当前聊天完全解耦。81 个任务各跑各的，互不干扰。

现在迁到 DeepSeek Harness，发现定时任务（或当前可用的调度方式）是绑定对话的——81 个任务全部落在同一个对话里，改一个任务要翻半天历史，执行记录和日常聊天混在一起，完全没法正常维护。

我知道 DSH 是插件化架构，调度层本身可替换。想找的是不把任务绑死在创建对话上的方案，类似 WorkBuddy 的模式：

• 任务独立创建、独立管理，不依赖某个“宿主对话”存活；
• 每次执行使用独立 Session，或至少不把提示词注入回创建时的会话；
• 最好有 Web 管理面板，能批量查看、启停、编辑 81 条量级的任务。

我目前了解到 DSH 生态里有几个社区插件可能接近这个方向，但不确定哪个对“81 条任务、不绑对话”的支持最稳：

• @liushutan/dsh-automation — 每次执行“fresh root Agent and Session”，不继承源对话历史；
• dsh-plugin-automations（Sev7een） — 明确“每次执行使用独立 Session”，支持 cron + once；
• dsh-polling — 任务本身就是一个独立会话，出现在侧边栏“轮询”工作区；
• dsh-schedule-tasks — 支持 headless / 独立进程运行，侧边栏管理面板。

想请教有实际使用经验的朋友：

1. 以上哪个（或还有其他插件）最接近 WorkBuddy 那种“建完就丢在那儿、每个任务独立跑”的体验？
2. 在 81 条任务量级下，哪个插件的 Web 管理面板还能保持可操作，不会卡顿或混乱？
3. 如果插件路线都不理想，有没有外置调度 + headless DSH 调用的替代思路（比如系统 cron / n8n 之类触发 dsh 一次性执行）？
4. 这些插件在 DSH 版本升级后的兼容性怎么样，有没有已知的“升级即挂”的坑？

感谢任何实际经验或踩坑反馈。

---

English Version

Title: Help: Is there a WorkBuddy-style "standalone session" scheduler for DSH? 81 tasks crammed into one conversation is unmanageable

On WorkBuddy, creating a scheduled task was trivial—say it in chat, and the task lived in a separate automation list. Each run spun up its own independent session, fully decoupled from the conversation where it was created. I had 81 tasks running side by side, no interference.

Moving to DeepSeek Harness, I'm hitting a wall: scheduling appears to be conversation-bound. All 81 tasks ended up tied to a single conversation. Editing one means scrolling through a massive history, and execution logs are mixed with everyday chat. It's not workable.

I understand DSH has a pluggable scheduling layer. What I'm looking for is a non-conversation-bound model, similar to WorkBuddy's:

• Tasks created and managed independently, not tied to the lifespan of a "host conversation";
• Each execution uses a fresh / independent Session, or at minimum does not inject the prompt back into the creating conversation;
• A Web management panel that remains usable at the ~81-task scale—batch view, enable/disable, edit.

I'm aware of a few community plugins that seem to point in this direction, but I'm not sure which handles "81 tasks, not conversation-bound" most reliably:

• @liushutan/dsh-automation — starts each occurrence in a "fresh root Agent and Session", no source-chat history inherited;
• dsh-plugin-automations (Sev7een) — explicitly "each execution uses an independent Session", supports cron + once;
• dsh-polling — each task is its own session, surfaced in a sidebar "Polling" workspace;
• dsh-schedule-tasks — headless / standalone process support, sidebar management panel.

Would appreciate input from anyone who has actually run these at scale:

1. Which of the above (or any other plugin) comes closest to the WorkBuddy experience—set it and forget it, each task running on its own?
2. At 81 tasks, does any plugin's Web UI remain operable without becoming a mess?
3. If no plugin fits cleanly, is the external scheduler + headless DSH route viable (system cron / n8n triggering a one-shot dsh run)?
4. How stable are these plugins across DSH upgrades—any known "upgrade breaks it" traps?

Any real-world experience or gotchas would be greatly appreciated.

[PerryLink]

现在没有"每个任务独立会话"这层能力：定时任务绑在它被创建的那个 Session 上。

packages/schedule/schedule/README.md 的原话是把它作为 "follow-up messages in their original Session" 投递，到期时由 Host 把那个冷会话恢复起来再交付。所以 81 个任务挤在一个对话里，不是因为任务多了，是因为它们当初都创建在同一个会话里。

能做到的隔离是倒过来用：先新建一个专用会话，在那个会话里创建这一族任务。这样它们的投递、模型、preset 都跟着那个会话走，主对话不受影响；需要几组就建几个会话。

做不到的是让任务 A 投递到会话 B——任务记录里没有目标会话字段，只有它创建时的来源。

如果你的真实诉求是"每个任务一份干净上下文"，现在只能靠"一任务一会话"来近似；真要一等公民的独立运行体，得等上游把任务和会话解耦。