Bundle
dsh-status-hub
A bilingual status hub for DeepSeek Harness sessions, MCP servers, skills, plugins, and connection health.
- Source
- HUSTforever
- License
- MIT
- Updated
- Updated 2 days ago
Readme
# DeepSeek Harness Status Hub A browser-side DeepSeek Harness plugin that adds a status hub to the sidebar. It uses the shipped Web UI extension points and reads existing Host services without introducing another server. ## Install Install the prebuilt GitHub Release: ```powershell dsh plugin --profile web add https://github.com/HUSTforever/dsh-status-hub/releases/download/v0.1.0/dsh-status-hub-0.1.0.tgz ``` Restart `dsh web`, then use the Status Hub icon in the sidebar footer. After an npm release is available, `dsh plugin --profile web add dsh-status-hub` is equivalent. ## Views - Overview: connection, active sessions, plugins, MCP servers, and skills. - Sessions: live session list with running state and navigation. - MCP: configured `@deepseek-ai/dsh-mcp-client` Loader entries and lifecycle state. - Skills: the `skills/list` catalog for the currently selected session. - Plugins: the read-only global Loader inventory with search and failure state. ## Local development ```powershell pnpm install pnpm run build dsh plugin --profile web add . dsh --profile web --no-open --port 3081 ``` Open the authenticated local URL printed by `dsh`. The profile dependency remains linked to this checkout, so rebuild and restart after changing the client bundle. ## Compatibility The package follows the documented dual-face plugin contract: an empty Host `apply()` entry, a `dsh.bundle` profile layer, a `dsh.client` Web declaration, an exported `./client` bundle, and slot registration through `ctx.slots.inject()`. Its development dependencies target the `0.1.2-rc.1` Web packages installed with the current local Harness distribution. MCP status is Loader-level status. Harness currently exposes MCP tools through the tool registry but does not expose a dedicated browser Remote for per-server health, so this view reports configuration and Fiber lifecycle without probing external servers. ## Distribution `pnpm pack` creates a prebuilt tarball that users can install without approving a source-build script: ```powershell dsh plugin --profile web add ./dsh-status-hub-0.1.0.tgz ``` For GitHub source installs, the `prepare` script builds `lib/`; pnpm 10 and newer require users to approve that install-time build. Publishing the prebuilt package to npm provides the simplest installation path. See [MARKETPLACE.md](./MARKETPLACE.md) for the GitHub and `awesome-dsh-plugin` submission checklist.
Install
dsh plugin --profile web add github:HUSTforever/dsh-status-hub
Profile: web
With the hub plugin installed, ask your agent to install it by name — it resolves the same plan shown here.
dsh plugin --profile web add github:stvlynn/dsh.fish#path:packages/dsh-plugin-hub
install dsh-status-hub from the hub
- This package builds from source on install. pnpm will ask you to allow its build script — that is permission to run the package’s code on your machine, outside the agent sandbox. Only allow sources you trust.
- This source has no pinned commit, so a later push upstream changes what installs. Prefer pinning a commit.