dsh-dashboard

dsh-dashboard

Unofficial third-party plugin — not affiliated with, sponsored, or endorsed by DeepSeek AI.

Session Dashboard for DeepSeek Harness — every session, task progress, waiting-for-approval states, background jobs and token/KPI metrics on one page, injected straight into the harness web GUI. No separate server or page.

Features

• Sidebar trigger — Dashboard toggle + sticky pin; icon-only rail mode with tooltips when the sidebar is collapsed
• Full-screen panel (never covers the sidebar):
  • 18 KPI tiles, tone-coded (running blue / completed green / waiting amber / errors red) — the status tiles double as clickable filters
  • Search + status filter chips with status dots (All / Running / Approval / Needs input / Errors / Completed / Idle)
  • Session tables with labeled status pills, keyboard support (Enter opens, D opens details), sticky column headers
  • Attention ripple on sessions waiting for user approval/input
  • Workspace grouping, live job activity feed, subagent hierarchy tree
  • Slide-over detail drawer: todo progress, live jobs, session stats, token-usage composition with legend, context-pressure gauge
• Floating live summary (sticky) — follows you across pages, minimized pill with a waiting counter
• Notifications — in-page toasts + audio chimes + native OS banners for completed / error / waiting states, wired through a requestAnimationFrame frame bridge so they fire even when the tab is unfocused
• Status model splits approval / question / plan-review out of pendingInteraction; errors come from crashed producer jobs
• Colors ride DSH design tokens (--dsw-*) — light/dark theme for free; respects prefers-reduced-motion

Requirements

• A running DeepSeek Harness install with the web GUI (this plugin only ships a client bundle)
• Node.js >= 18 (only needed when building from source)

Install

One command (recommended)

The package is a profile bundle: it declares dsh.bundle.patch, so the harness CLI installs it and stacks its patch layer automatically — no manual cordis.patch.yml edits.

From a local checkout (no npm publish needed):

# run from this repo's directory
dsh plugin --profile web add .

# or from anywhere, with an absolute path
dsh plugin --profile web add C:/path/to/dsh-dashboard

From GitHub (pnpm git install of the prebuilt lib/):

dsh plugin --profile web add github:jinhun-tqtteam/dsh-dashboard

From npm (once published):

dsh plugin --profile web add @jinhun-tqtteam/dsh-dashboard

The command adds the package as a profile dependency, appends it to dsh.profile.bundles (its dsh.bundle.patch declares the loader entry), and restarts pick it up.

Manual (no CLI)

Copy the package folder (with the prebuilt lib/) into the profile's plugin store and register the loader entry by hand:

<profile>/web/node_modules/@jinhun-tqtteam/dsh-dashboard

Add to <profile>/web/cordis.patch.yml:

- insert:
    - id: dsh-dashboard
      name: "@jinhun-tqtteam/dsh-dashboard"

The loader entry name must exactly equal the bundle's registered id (the package name). The client module graph rejects a bundle that registers a different id.

Restart

Plugin-set changes need a harness restart; bundle-only changes reach the graph via a browser refresh.

Usage

Notification sounds & banners

The first bell click warms the audio context, asks for window-notification permission and starts a keep-alive so background tabs never silence alerts.

If the bell dot stays amber:

1. Allow notifications for the harness origin in the browser (padlock icon in the address bar).
2. Check the OS-level setting for the browser app, e.g. Windows Settings -> System -> Notifications.

How it works

The package registers one host-side plugin (an empty apply, purely to appear in the Loader) and one client bundle served at /plugins/@jinhun-tqtteam/dsh-dashboard/client.js. The bundle registers itself through window.__ModuleLoader__.load in the lazy-CJS shape the DSH client module system expects, mounts three shell.overlay entries (panel, sticky, notifications) plus one sidebar.footer.action entry (the trigger), and receives the openSession descriptor through the standard inject mechanism.

src/ is the source of truth; lib/ is committed so the manual copy install works without a build step.

Development

npm install
npm run build   # esbuild src/ -> lib/client.js (ModuleLoader CJS shape)
npm run smoke   # structural checks: bundle shape, slot registration, exports

The build fails if the bundle comes out suspiciously small. CI runs build + smoke on Ubuntu, Windows and macOS.

See CONTRIBUTING.md for the full contribution guide.

Troubleshooting

License

MIT © Tran Quang Tien