At a Glance

Add a "Task DAG" entry to the DSH Web session title bar that renders the current session, its delegated sub-agents, and persistent workflow nodes into a top-down dependency graph. Nodes are draggable and clickable for navigation—a visualization tool for troubleshooting "what sub-tasks were derived from this task and which step are they at."

Core Capabilities

• Real-time Topology: Converts DSH's existing client projection into a top-down DAG; the graph refreshes when session state changes without Host-side polling
• Persistent Workflow Recovery: After DSH restarts, reconstructs workflow stages and members from workflow-run session nodes, preserving context without loss
• Workflow Grouping: Collapses workflow members under workflow nodes to avoid drawing duplicate direct edges from the root session to members
• Direct Navigation: Click (or press Enter/Space) on healthy sub-agent nodes still in the Session list to jump directly to the corresponding session
• Canvas Controls: Switch between "Fit All" and "Original Size Scrollable" views; drag empty areas to pan the canvas
• Node Drag Repositioning: Drag nodes to re-layout; edges follow in real-time; adjusted positions persist when the current Session is closed and reopened
• State Visualization: Colors are restrained to business blue/success green/error red/warning amber四种; other levels are expressed through spacing, fonts, borders, and line styles
• Safe Uninstallation: UI and styles are registered through Cordis lifecycle; completely removed when the plugin is uninstalled with no DOM residue

Technical Implementation

• Language: JavaScript (src/client.js uses CommonJS, src/graph-model.js uses ESM, scripts/build.mjs uses ESM)
• Key Dependencies: @deepseek-ai/dsh-client-runtime / @deepseek-ai/dsh-client-locale / @deepseek-ai/dsh-client-ui-conversation / @deepseek-ai/dsh-client-ui-primitives / @deepseek-ai/dsh-client-ui-workflow-run / react ^18.2.0
• Architecture Pattern: Pure Cordis client plugin; cordis.patch.yml registers a plugin named task-dag in the host; apply(ctx) injects TaskDagAction into the session title bar via ctx.slots.inject('conversation.session.header.actions'), uses ctx.effect to register stylesheets and Chinese/English dictionaries, and collapses the catalog via ctx.sessions.setSubagentCatalogOpen when closing the panel; the DAG is computed by pure functions buildGraph + graphLayout, with UI rendered via React + ReactDOM Portal to document.body
• Entry Files: src/client.js (UI components) + src/graph-model.js (bloodline normalization, workflow grouping, deterministic vertical layout), bundled by scripts/build.mjs into browser-loadable lib/client.js

Use Cases

For users responsible for managing multi-Agent collaboration sessions: when a Session spawns many one-off sub-agents or persistent sub-agents, and you want to instantly see "which step is still running, who spawned whom, and which workflow stage they belong to." Suitable for demo scenarios and on-site troubleshooting of complex multi-step tasks, avoiding the need to scroll back and forth in the sub-session list.

Prerequisites & Compatibility

Installation

dsh plugin --profile web add github:LeemanCheung/dsh-task-dag

Configuration

No additional configuration required. After installation, restart dsh web once, and the "Task DAG" entry will appear in the session title bar—no files or environment variables need to be edited.

FAQ

Q: I don't see the "Task DAG" entry in the session after installation. What should I do?

A: Confirm the profile is web (add --profile web to the command). First-time installation requires restarting the dsh web process and refreshing the browser page; subsequent enablements or upgrades typically don't require a restart.

Q: Clicking a node doesn't open the corresponding session. What should I do?

A: Only sub-agent nodes that still appear in the DSH Session list are navigable; if a session is archived, deleted, or not currently visible, its node won't respond to clicks. Use the "Refresh" button in the panel to re-fetch the sub-agent catalog.

Q: I dragged nodes to adjust their positions. Will they persist for the next session?

A: Positions are only preserved in the current page's React state for the current Session. After switching to another Session, refreshing the page, or restarting DSH, it will return to the plugin's deterministic auto-layout; the workflow topology itself is still rebuilt from persistent workflow-run data.

Q: Does this plugin read my files, make network requests, or inject prompts?

A: No. This is a read-only visualization plugin that runs entirely in the browser; it doesn't read workspace files, send network requests, register model tools, or persist session content or credentials. See SECURITY.md for details.

Q: Is CLI or Desktop profile supported?

A: No. package.json dsh.client.platform explicitly declares "web", and cordis.patch.yml only registers a client-side plugin with no node-side implementation.

Q: The status or labels in the graph look outdated. What should I do?

A: The panel automatically fetches the observed sub-agent catalog upon opening; if there's a discrepancy, click the "Refresh" button in the toolbar to fetch again. Workflow nodes are always driven by persistent data projection; the refresh button won't rearrange workflow ownership.

Q: How do I uninstall?

A: Run dsh plugin --profile web remove dsh-task-dag, then restart dsh web once.

Ease of Use

Beginner — Plug and play with no config files or environment variables; click the entry to open the graph, drag nodes, click to navigate, and other interactions are all GUI-based—no code or command-line operations required.

Known Issues & Limitations

• Layout preservation is bounded: manually dragged node positions are only stored in the current page's React state for the current Session; switching Sessions, refreshing the page, or restarting DSH returns to deterministic auto-layout, see source code at src/client.js:549 useEffect(() => { setNodePositions({}); }, [sessionId])
• Workflow member attribution uses "last resolved workflow" to overwrite previous attribution and status, so if the same sub-agent is referenced by multiple workflows simultaneously, it will be grouped under the last resolved workflow, see source code at src/graph-model.js:170-175
• Projection discards orphans that cannot be traced to the current Session, missing parent node chains, and circular bloodlines, while still generating deterministic vertical levels for legitimate deep dependency chains, see source code at src/graph-model.js:72-91
• Status colors are intentionally limited to business blue, success green, error red, and warning amber四种; other levels (workflow vs sub-agent vs root session) are distinguished only by icons, spacing, borders, and line styles, see source code at src/client.js:69 (zh dictionary status.*) and README.md:71
• No focus trap: when the panel is open, only Escape to close and return focus to the entry button; keyboard dragging of panel, canvas, or nodes is not supported, see source code at src/client.js:558-568 and README.md:69
• Current check pipeline (npm run check) only covers syntax, pure model unit tests, and jsdom smoke testing; theme visuals, responsive layout, focus, and uninstallation behavior in real profiles still require manual or browser E2E verification, see source code at README.md:114-115

dsh-task-dag

A live task topology for DeepSeek Harness Web.
See Sessions, delegated subagents, and durable workflows as one navigable DAG.

English · 中文

At a glance

dsh-task-dag turns DSH's existing Client projections into a top-to-bottom dependency graph. It keeps no parallel workflow database and sends no polling requests: when Session state changes, the graph changes with it.

Live screenshot

Captured from a running DSH Web Session with task labels anonymized. The panel, layout, edges, controls, and status presentation are the actual plugin UI.

Install

dsh plugin --profile web add github:LeemanCheung/dsh-task-dag

Restart the current DSH Web process once after the first installation, then refresh the page. The Task DAG action appears in the Session header.

For a version-pinned installation:

dsh plugin --profile web add github:LeemanCheung/dsh-task-dag#v1.2.0

Using the graph

Status colors are deliberately limited to business blue, success green, error red, and warning amber. All other hierarchy is expressed through spacing, typography, borders, and line styles.

Architecture

The browser plugin combines three durable Client-facing sources:

• SessionListState.byId and parentId provide subagent lineage.
• SessionListState.subagentsByParent provides labels, modes, activity, and catalog health.
• workflow-run Conversation Nodes provide workflow phases, members, and outcomes.

The package-owned graph-model Module normalizes lineage, inserts workflow grouping nodes, derives navigation capability, and lays out stable vertical layers. The UI Module renders that projection into conversation.session.header.actions.

There is no process-local workflow cache, model prompt contribution, model tool, Host RPC endpoint, or polling loop.

Projection boundaries

Only descendants that can be traced to the current Session through origin: "subagent" lineage are shown. Orphans, missing-parent chains, and cycles are ignored. A catalog's running activity takes precedence over a completed Session summary; workflow members use their workflow-run status; unknown statuses render as historical/idle. If the same member appears in more than one workflow, the last parsed workflow membership owns its displayed grouping and status.

Security and permissions

This is a browser-only, read-only visualization plugin. It does not read workspace files, execute commands, open network connections, register model tools, or persist Session content and credentials.

See SECURITY.md for the reporting policy and complete trust boundaries. Private vulnerability reporting is enabled for the repository.

Development

The runtime package declares Node.js 20+. For development and the pinned jsdom test stack, use Node.js 20.19+, 22.13+, or 24+; CI currently runs Node.js 22.

npm install
npm run check

The check pipeline:

1. validates source syntax and the pure graph-model Module;
2. runs graph-model unit tests for lineage, workflow grouping, deterministic layout, and deep chains;
3. rebuilds and validates the precompiled browser module;
4. runs jsdom interaction smoke tests for controls, canvas panning, persistent node dragging, and node navigation;
5. verifies in CI that committed lib/client.js is reproducible from source.

These are pure-model and jsdom smoke checks, not a full DSH Web end-to-end suite. Theme fidelity, responsive layout, complete focus behavior, and unload behavior in a real profile still need manual or browser-E2E verification.

scripts/build.mjs embeds src/graph-model.js, src/client.js, and src/style.css into the committed lib/client.js. Do not edit that generated file directly: change src/, then run npm run build or npm run check before committing.

Troubleshooting

Remove

dsh plugin --profile web remove dsh-task-dag

License

MIT © LeemanCheung