dsh-task-dag

A live orchestration topology for DeepSeek Harness Web.
Inspect delegated Sessions, Agent Teams task dependencies and communication, and durable Workflow runs.

English · 中文

dsh-task-dag turns DSH's existing Client projections into three focused graph views. It keeps no parallel orchestration database and sends no polling requests: Session, Team, and Workflow state is rebuilt from the projections DSH already owns.

Additional behavior:

• Agent communication: directed channels aggregate message count and queued delivery state. Select a channel to inspect the latest 100 message records with quiet/wakeup and delivery metadata; only text blocks are previewed, while other block types are counted.
• Agent runtime metrics: hover or keyboard-focus a teammate, subagent, or Workflow member to see the latest request Provider, model, concrete DSH effective reasoning-effort ID when one was durably recorded, its recorded source, and whole-Session cumulative input, output, cache, turn, and step totals. An effort materialized by DSH from Adapter defaults is labeled Adapter default; otherwise a recorded effort is labeled Request config without claiming whether it came from a preset, plugin, middleware, user choice, or an older Adapter. When the request omitted effort, the actual field remains Not recorded; an exact public model default may appear on a separate reference row and is never presented as proof of that historical call. GPT-5.6 Terra's OpenAI API model-page reference is medium; the UI explicitly says this is not a record of the request.
• Direct navigation: selectable teammate, subagent, and Workflow member nodes open the real Session when it remains visible in the Session list.
• Workflow definition preview: select a Workflow run node to inspect the exact JavaScript orchestration body, definition summary, usage guidance, and declared phase metadata from its matching workflow tool call. The native code block can copy the full script; runtime args are deliberately not projected.
• Canvas control: fit the whole topology, pan the original-size canvas, or drag nodes while connected edges update.
• Per-view layout: manual positions survive view switches and reopening the panel for the current Session. Switching Sessions, refreshing the page, or restarting DSH restores deterministic automatic layout.
• Native presentation: the panel uses DSH semantic theme tokens, accessible status labels, edge line styles, responsive communication details, and reduced-motion behavior.
• Lifecycle safety: Team projection, locale, styles, and Slot UI are all owned by the Cordis plugin lifecycle.

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

Select a Workflow run to open the v1.4.0 definition inspector beside the live topology:

The v1.4.0 UI has been exercised in real DSH Web Sessions in addition to the model and jsdom checks:

The Workflow fixture returned alpha-ok, beta-ok, and summary-ok; the browser console reported zero errors during both checks. The Session-header badge counts related topology nodes and excludes the current Session, while the dialog total includes that root. A badge of 6 therefore corresponds to 7 nodes in the open Workflow graph.

To reproduce the Workflow check, create a new top-level Session, invoke the workflow tool from that Session, then open Task DAG → Workflow in the same Session. If Workflow is invoked inside a subagent, open that child Session first; the parent graph correctly shows the child as delegated work rather than adopting its internal Workflow run.

dsh-task-dag visualizes Agent Teams records but does not install or create the Agent Teams runtime. At the time of this release, Agent Teams is an upstream experimental capability and is not mounted by every stock DSH Web profile. The Host composition must emit the supported Team events before the Agent Teams view can contain data.

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.5.0

The dialog does not trap focus and does not provide keyboard dragging for the panel, canvas, or nodes.

The plugin combines six durable projections and Client-facing sources:

• The Host-side taskDagAgentMetrics Session projection folds only the latest request/header Provider, model, concrete effective reasoning-effort ID, and the adapterDefaults.reasoningEffort source marker. DSH's tokenUsage and sessionStats projections provide whole-log cumulative values.
• SessionListState.byId and parentId provide ordinary subagent lineage.
• SessionListState.subagentsByParent provides labels, modes, activity, and catalog health.
• Durable Agent Teams events provide members, shared tasks, queued messages, and delivery acknowledgements.
• workflow-run Conversation Nodes provide Workflow runs, phase groups, members, and outcomes.
• Matching tool-call Conversation Nodes provide the already-visible raw workflow input. The plugin parses only its script and definition metadata, then associates it with the nearest same-name run in event order.

A package-owned hidden Conversation Node Definition projects each supported Team v1 event into a small snapshot node. The graph model folds the latest task/member state, matches message delivery acknowledgements, aggregates directed communication channels, constructs explicit multi-parent edges, and applies a deterministic non-recursive topological layout. The UI renders the result in conversation.session.header.actions.

There is no model prompt contribution, model tool, Host RPC endpoint, network request, polling loop, or second persistence layer.

• Agent Teams writes the task board and message journal into the Team Lead Session. A teammate Session cannot read that log across Sessions, so its Team view links back to the visible parent Session instead of adding a cross-Session Host RPC.
• Runtime metrics come from registered whole-log projections. Token values are cumulative. Provider, model, and reasoning effort are the latest values in DSH's normalized request header; they are not reasoning-token counts or raw Provider wire parameters. Adapter default is shown only when the durable header records that marker. src/reasoning-defaults.js contains source-attributed public references for exact routes, but those references never replace a missing request value or service response.
• blockedBy is the only edge presented as a real Team task dependency. Communication can be bidirectional and cyclic, so it is an overlay and never participates in DAG layering.
• Persisted Workflow phases are progress groups. They do not reveal the complete internal parallel() or pipeline() control flow and are not labeled as execution dependencies.
• Definition preview requires the matching workflow tool-call head to remain in the current Session window. If compaction or truncation removes it, the durable run topology remains visible and the inspector explains that the definition is unavailable; the plugin never guesses or reconstructs missing code.
• Ordinary lineage must trace to the current Session through origin: "subagent". Orphans, missing-parent chains, and lineage cycles are ignored. Malformed dependency cycles receive a deterministic fallback layer rather than blocking rendering.
• The same Session may appear in Team and Workflow contexts because those nodes communicate different ownership semantics; all appearances navigate to the same Session ID.

This is a read-only visualization plugin. The Host half folds only Provider, model, reasoning effort, and its source from request/header into a small Session projection; the Client may add a clearly separated reference from the audited static Provider-default table. The plugin does not read workspace files, execute commands, open network connections, register model tools, or persist new Session content or credentials. Message previews and Workflow code come only from records already visible in the current Session, and appear on demand after the user selects a communication channel or Workflow run. Runtime Workflow args, system prompts, and tool schemas are excluded from the metrics projection.

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

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 validates all source syntax; tests request-config, Adapter-default, separated public-default references, unrecorded, legacy, and contradictory reasoning evidence, Team event projection, task and communication folding, Workflow definition extraction and run matching, Workflow grouping, arbitrary DAG layout, deep lineages, and cyclic fallback; rebuilds the Host and browser artifacts; then runs jsdom interaction coverage for three views, pointer and keyboard Agent metrics, focus-after-scroll, narrow viewports, non-navigable Agent nodes, communication timeline, Workflow code inspector, canvas controls, per-view node positions, and Session navigation. CI rejects drift in both committed Host and browser output.

These are pure-model and jsdom checks rather than a complete DSH Web E2E environment. Before release, the linked package is additionally verified against the running Web profile in a real browser.

scripts/build.mjs copies src/index.js and src/reasoning-defaults.js into the Host lib/ entries, then embeds the same reasoning-default resolver plus src/team-projection.js, src/workflow-definition.js, src/graph-model.js, src/client.js, and src/style.css into committed lib/client.js. Do not edit generated files directly.

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

MIT © LeemanCheung