MiloMMIN/dsh-agent-board
Cross-Agent workbench: dsh persistent plugin that watches Claude Code / Codex / Kimi Code / Pi / Hermes and continues the
A cross-agent workbench: it watches every local coding agent (Claude Code, Codex, Kimi Code, Pi, Hermes), shows what they are doing right now, and hands their work over to a fresh dsh session in the correct workspace with one click. The README documents a live board (sidebar panel plus a standalone /agent-view page, auto-refreshing), a agent_board model tool that lets the agent itself report what the other agents are doing, and a settings page with every behaviour configurable. Clicking a session row resolves or creates the workspace for that session's root directory (merging rather than duplicating existing workspaces), opens a new session there, renames it to short-task-description--agent, and sends a structured handoff brief naming the source agent, session id, working directory, task summary, work status and timestamps. Settings include refreshSeconds, activeMinutes, perAgentLimit, titleDescChars, fallbackCwd, autoConfirm and autoClosePanel.
Install
pnpm add dsh-agent-board@link:<absolute-path-to-dsh-agent-board>README installation, quoted verbatim: this is a profile-level persistent plugin for the web profile (not a dynamic plugin). Place the package in the profile (the README suggests ~/.dsh/profiles/web/plugins), then in ~/.dsh/profiles/web run pnpm add dsh-agent-board@link:<abs path to dsh-agent-board> — or add "dsh-agent-board": "link:<abs path>" to package.json dependencies manually — then insert the plugin row into the profile patch layer and restart dsh web. The README's patch row is: - insert: - id: agent-board name: dsh-agent-board No npm release is claimed — dsh-agent-board is not published on the public registry (404 verified 2026-09-13), so the link: dependency is the documented path.
Compatibility
DeepSeek Harness web profile, installed as a profile-level persistent plugin. The README notes the scanner also talks to Hermes through its CLI (hermes sessions list, hermes project show) — sessions without a resolvable directory fall back to the configurable default workspace, which defaults to the user's home. It reads the session stores of other agents read-only.
Details
- Repo: MiloMMIN/dsh-agent-board
- Category: Agent Capabilities
- Stars: 2
- Version: Local link: dependency + profile patch row (README's documented form; no npm release — dsh-agent-board returns 404 on the public registry, checked 2026-09-13)
- Last push: 2026-08-14
- First seen: 2026-08-14
Recent updates
The README documents the feature set, the install steps and the settings table rather than a versioned changelog; there is no release history or migration section, and no npm version is published. Session stores are read read-only. Verify the current install instructions in the repository before installing.
FAQ
- How do I install dsh-agent-board?
- Copy the package into the web profile (the README suggests ~/.dsh/profiles/web/plugins), add it with pnpm add dsh-agent-board@link:<abs path> from the profile directory, insert the agent-board row into the profile's cordis.patch.yml, then restart dsh web.
- Which agents does it watch?
- Claude Code, Codex, Kimi Code, Pi and Hermes — read-only from their session stores; Hermes is also queried through its CLI (hermes sessions list / hermes project show).
- How does the handoff work?
- Clicking a session row resolves or creates the workspace for that session's root directory, opens a new session there, renames it 描述--agent, and sends a structured brief (source agent, session id, working directory, task summary, status, timestamps) that the new session builds on.
Alternatives
LeslieWylie/dsh-task-relay · leemancheung/dsh-task-dag · vlln/dsh-task-status