LeslieWylie/dsh-task-relay
DSH cross-session task relay board: task_push/list/claim/done + handoff_write/read
Cross-session task relay board: a persistent shared task queue with handoff notes so sessions (including subagents) can coordinate. Push tasks to future sessions (task_push), list/filter open tasks (task_list), claim and complete them (task_claim / task_done), cancel (task_cancel), and record session handoff summaries (handoff_write / handoff_read) so the next session knows what was done. Fills the gap where DSH session A's work is invisible to session B by default.
Install
dsh plugin --profile web add github:LeslieWylie/dsh-task-relayGitHub install per README (English edition README.en.md): dsh plugin --profile web add github:LeslieWylie/dsh-task-relay (also for headless profile). Or add - id: task-relay, name: 'dsh-task-relay' to cordis.yml. No npm package.
Compatibility
DeepSeek Harness web / headless profiles. All data stored at $HOME/.dsh/task-relay/queue.json with atomic writes (temp file + rename).
Details
- Repo: LeslieWylie/dsh-task-relay
- Category: Other
- Stars: 3
- Version: GitHub source (no npm package)
- Last push: 2026-08-18
- First seen: 2026-08-14
Recent updates
7 tools: task_push/list/claim/done/cancel + handoff_write/read; JSON file store with atomic writes; config.root override per profile.
FAQ
- What problem does it solve?
- DSH sessions are independent — work done in session A is invisible to session B. This adds a shared queue + handoff notes for cross-session and subagent coordination.
- Where is data stored?
- $HOME/.dsh/task-relay/queue.json, written atomically (temp file + rename) to prevent corruption; override the directory with config.root.
- Can subagents use it?
- Yes — any session including subagents can push, claim, complete, and cancel tasks, and read handoff summaries.
Alternatives
shaokeyibb/dsh-plugin-product-subagents · icetomoyo/dsh_workflow · omdsh-dev/dsh_workflow