dshbase

Plugin directory / Data / DSH-Plan-Graph

DSH-Plan-Graph

Verified · install-tested on dsh HR2AY

✓ Actively maintained 2 contributors

View on GitHub ↗ ← Back to plugin directory

15Stars
1Forks
0Open issues
JavaScriptLanguage
2026-08-16Last push
Cross-platformPlatform

What it does

another version of deepseek herness trajectory (DIY)

Our take
Works — verified, early-stage project

another version of deepseek herness trajectory (DIY) It installs cleanly and boots without issues in our testing. It's early-stage but functional.

“Verified” means our automated CI actually ran dsh plugin add in a clean profile and it booted — nothing more. Feature descriptions and version compatibility are the author’s claims. This is not a security audit and not an endorsement of third-party code.

README

8/16更新

dsh-plan-graph

An out-of-tree DeepSeek Harness plugin bundle: an interactive flow graph of a session's tool calls and messages, rendered client-side from the conversation snapshot. The plugin adds a "Plan Graph" tab to the session view ring (pan/zoom canvas, status-colored node cards, node details, hide-tool-calls and group-by-turn toggles, follow latest, and "Merge into conversation" into the real right sidebar).

pkg-3 adds three features on top of the graph:

  • Favorites — a panel centered at the bottom of the view, opened from the toolbar button (colored kind tiles + summary + time). Per-session, persisted as JSON in localStorage under dsh.plan-graph.fav.<sessionId>, deduped by node id, capped at 100. Add via the node context menu or by dragging a node onto the toolbar favorites button. Click an entry to center the graph on that node with a flash highlight; if the node has left the current window (partial finished, node paged out), the click falls back to the matching chat row by seq/callId. Removal goes through the node context menu.
  • Node context menu — right-click a node for: add/remove favorite, locate in conversation (tool-call nodes only), copy node info, view details. Closes on outside click, Escape, or canvas interaction. Favorites are managed here (and by dragging a node onto the toolbar favorites button) — there is no ★ button on the details panel.
  • Locate in conversation — maps any node to its chat row: tool calls by callId, assistant output by data.finalNode.seq, and user input / steering / context by data.seq (the same event seq the graph node id embeds), then waits for the data-chat-flow-key anchor via MutationObserver, scrolls it into view and flashes it; a 10s timeout silently falls back to in-graph locate. Prefers an upstream chatLocate optional service when a deployment provides one.

The browser half is the plan-graph dynamic-plugin code (pkg-3), wrapped in the web module loader's handoff format — plain JavaScript, no build-time dependencies. The prepare script (which pnpm runs after a git install) regenerates client.js from client.body.js.

Changes since 0.1.0 (pkg-20): pkg-21 — user/steering nodes display「输入」(input) and context nodes「已完成」(completed) instead of idle; pkg-22 — dragging the canvas no longer selects text (user-select: none + preventDefault on mousedown); pkg-3 — favorites (persisted, drag-to-add), node context menu, and locate-in-chat; pkg-4 — the graph flash highlight clears itself via the CSS animation's animationend (the dynamic client half withholds browser timer globals, so setTimeout is not used); pkg-5 — favorites UI is the dropdown-panel form (colored kind tiles + summary + locate pin + details ★ button); pkg-6 — the panel renders centered at the bottom of the view and the per-entry × remove button is dropped; pkg-7 — the context menu reorders so 定位至对话区 (locate-in-chat) sits below the favorites toggle; pkg-8 — the chatNodeVisibility service gains subscribe(fn) (its consumer calls it during Chat render; without it the conversation page went blank when switching back to Chat); pkg-9 — 定位到图内 removed from the context menu, the details ★ button removed (favorites via context menu only), and favorites entries store the node seq with a chat-row fallback when the node leaves the window; pkg-10 — the locate-pin icon is dropped from favorites rows; pkg-11 — 定位至对话区 works for every node kind (tool by callId; assistant by finalNode.seq; user/steering/context by data.seq).

Install

From a directory that contains this package (or any npm registry / tarball / git host):

dsh plugin --profile demo add ./plan-graph-bundle
dsh --profile demo
  • From GitHub (sources, not built artifacts — the prepare script builds on install): dsh plugin --profile demo add github:<you>/plan-graph-bundle#<sha>. pnpm refuses to run the prepare script until it is allowlisted — copy the exact package key pnpm printed into the profile's pnpm-workspace.yaml:

    allowBuilds:
      dsh-plan-graph: true
    

    and re-run the add. That allowance is permission to execute this package's code on your machine at install time — pin a commit (#<sha>) and only install sources you trust.

  • From a tarball (no build permission needed): pnpm pack in this directory, then dsh plugin --profile demo add ./dsh-plan-graph-0.3.0.tgz.

  • From npm (once published): dsh plugin --profile demo add dsh-plan-graph.

Verify the layer without booting: dsh --profile demo --dump-config shows a # == dsh-plan-graph layer.

What it needs

  • The browser half registers into conversation.view / details through the standard client plugin services (slots, locale, layout), all provided by the dsh web surface.
  • "Hide tool calls" provides the optional chatNodeVisibility service. The shipped ui-conversation does not consume it yet, so against an unpatched dsh the toggle hides nothing on the chat page (the graph itself honors it); deployments with a ui-conversation that consumes the service get the live chat filtering.
  • Fresh sessions keep Chat as the default view; the Plan Graph tab is one click away. A deployment that wants the graph front and center provides the upstream conversationDefaultView service itself ({ id: 'plan-graph' }).
  • "Locate in conversation" reads the shared conversation snapshot and targets the chat row's data-chat-flow-key anchor. The anchor is a view-layer contract of the shipped chat view; if a future dsh renames it, the feature silently falls back to in-graph locate rather than erroring.

Regenerating the client bundle

npm run prepare (or node scripts/build-client.mjs) rewrites client.js from client.body.js. Edit the body, never the generated file.

Install

🧩 Let your agent install it (recommended)

Install the catalog once, then DeepSeek Harness can find and install any plugin from this site automatically:

dsh plugin add dshbase-catalog

Then say "install DSH-Plan-Graph for me" — your agent finds it in the directory and installs it. Docs: dshbase-catalog · verified packs.

This plugin is GitHub source (not published to npm) — install it straight from the repo:

Web profile:

dsh plugin --profile web add github:HR2AY/DSH-Plan-Graph

Headless (CLI) profile:

dsh plugin --profile headless add github:HR2AY/DSH-Plan-Graph

Test report

Verified: L1 install + L2 load + L3 runtime from GitHub source on dsh 0.1.0-rc.6.

When to use it

Let the agent crunch data — parse, transform, or analyze — so it works with real datasets, not just prose.

Who it's for

Users whose tasks involve tables, files, or numbers that need processing or analysis.

For developers — extending it

Data sources and transformation tools are the seams — add formats, aggregations, or visualization outputs.

Security: not yet scanned — our daily static scan will cover it shortly.

Share this badge

More in Data

Browse all 7795 plugins →