BundleWeb UI / Observabilityv0.1.12Developer Preview

Live Stats

Live Stats is a DeepSeek Harness Web bundle for displaying documented token estimates and generation throughput alongside conversation activity.

1,442 repository starsApache-2.0 Updated Aug 14, 2026

Review snapshot

Manifest
Passed
Install
Not tested
Runtime
Not tested

Static compatibility snapshot dated 2026-08-14; install and runtime remain independent checks.

Install / upstream documentation

Install the pinned release deliberately

This bundle uses an upstream-documented installation path pinned to the reviewed release. Read the linked README and inspect the source before you install it.

See GitHub README

Upstream command · profile web

dsh plugin --profile web add @linxin666/dsh-live-stats@0.1.12

This version-pinned npm command uses the reviewed package name. Restart dsh web after installation as upstream directs. AgentPlugin.net did not execute the command, so it is not a compatibility or safety guarantee.

Source: Pinned upstream README

Plugin brief

What Live Stats adds to DeepSeek Harness

Live Stats is one independently packaged part of the dsh-web-ui collection for the DeepSeek Harness Web profile. Its reviewed package manifest declares a DSH bundle patch and a Web client integration, while its Cordis patch adds the exact npm package to the profile roster. live token estimates, throughput, and the usage signals documented by the upstream Web interface. This evidence establishes the project’s stated integration shape, not a promise that a particular host version, profile, browser, or workspace will behave the same way. The entry therefore separates what upstream documents from what this directory has tested: manifest structure passed static inspection; install and runtime remain not tested.

Evaluate Live Stats as a profile extension with access appropriate to its feature area, rather than as a passive theme or documentation page. The package can participate in a local DSH host process and its browser client can add controls to the Web interface. Use a disposable profile or non-sensitive workspace for an initial evaluation, read the pinned source before granting build approvals, and keep normal review practices around commands, files, network access, and configuration. A version pin makes the referenced npm release unambiguous, but it does not freeze DeepSeek Harness or prove the upstream release is compatible with every developer-preview installation.

The dsh-web-ui repository also publishes an aggregate package, but this page records a single selectable component so readers can judge its purpose and risk independently. Installing the aggregate package may add more capabilities and different trust boundaries than this entry alone. Conversely, a package that appears in a collection can still require host services, browser injections, a restart, or build approval. Check existing profile patches before changing anything and avoid treating a visible sidebar button or panel as evidence that a feature is safe, authorized, or fully verified. Upstream documentation is the primary source for current operational instructions.

Evaluation workflow

Evaluate Live Stats with clear boundaries

01

Begin with the pinned @linxin666/dsh-live-stats@0.1.12 package and a Web profile you can recover. Confirm the DSH command-line tool and profile name before copying the install command, then restart dsh web only after the package manager completes. If the host does not load the expected UI, inspect the pinned manifest and Cordis patch rather than adding duplicate manual mounts. The upstream guide notes that profile directories are not pnpm workspaces, so local linking and aggregate dependencies have different resolution behaviour from a normal repository workspace.

02

Read the feature controls before using them on meaningful work. Live Stats is documented for live token estimates, throughput, and the usage signals documented by the upstream Web interface. Keep source control, backups, credential boundaries, and human approval in place. A plugin can present a polished Web interface while still reaching host-side services or changing DSH configuration. Do not use a catalog listing as an authorization decision, and do not assume a static manifest check covers data handling, performance, permission checks, or all error paths in the running package.

03

Treat updates as a new evaluation. The repository documentation says that package releases can lag source builds and describes an earlier Pet release with missing runtime files. Keep the version pinned for a repeatable review, compare release notes and source when moving to a newer version, and re-check the profile after an upgrade. If pnpm reports ignored builds, understand each dependency before allowing it; approval means code can run during dependency installation and is not merely a harmless warning.

Verification ledger

Evidence, not installation claims

Manifest

Passed

Static review passed: the pinned package.json names @linxin666/dsh-live-stats at 0.1.12, declares dsh.bundle.patch, and the pinned Cordis patch inserts that package into a DSH profile roster.

Checked Aug 14, 2026

Install

Not tested

No clean DeepSeek Harness Web profile installation was run by AgentPlugin.net.

Runtime

Not tested

No live host service, browser UI, permission boundary, or feature smoke test was run by AgentPlugin.net.

Source or manifest review can be recorded while Install and Runtime remain not-tested. Treat these as separate verification layers.

Execution surface

Prepare, build, and code-execution review

  • prepare

    not recorded

    No review record is available for this execution surface. Inspect the upstream repository before running it.

  • build

    review recorded

    Upstream documents pnpm ignored-build prompts for some dependencies. Build approval can execute dependency code and should be reviewed before it is granted.

  • code execution

    not recorded

    No review record is available for this execution surface. Inspect the upstream repository before running it.

  • configuration

    notice recorded

    The bundle changes a DSH Web profile through a Cordis patch. Review existing profile configuration and avoid duplicate manual mounts.

  • configuration

    notice recorded

    Usage figures and generation rates are presentation data from host integrations. Do not treat displayed estimates as an audited bill, quota decision, or independent measurement.

Third-party code can execute during dependency preparation, build, or runtime. Read the upstream source and its changes before use.

Declared scope

Capabilities and prerequisites

Capabilities

  • Display documented generation throughput information
  • Surface token and context-related estimates in the Web UI
  • Integrate with reviewed DSH session and token-meter peer dependencies

Prerequisites

  • A working DeepSeek Harness Web profile
  • A DSH release providing the required session and token-meter APIs
  • Acceptance that displayed figures are upstream-described estimates, not billing records

Frequently asked questions

Live Stats FAQ

What is Live Stats?

Live Stats is a DSH Web bundle from the dsh-web-ui repository. Upstream describes it as live token estimates, throughput, and the usage signals documented by the upstream Web interface. The package and Cordis patch linked on this page identify the exact package row reviewed for version 0.1.12.

Which DeepSeek Harness profile does this entry target?

The reviewed package declares a Web client platform and the upstream README documents installation into the web profile. That is a declared target, not a runtime compatibility certification from AgentPlugin.net.

Why is the installation command version-pinned?

A fixed 0.1.12 package name makes the command refer to the same release reviewed by this catalog entry. It avoids a latest tag changing underneath a reader, but does not eliminate dependency, registry, or host-runtime changes.

Has this plugin been installed and smoke-tested by AgentPlugin.net?

No. The manifest and patch were statically reviewed at the pinned commit. Installation in a clean profile and runtime behaviour are explicitly marked not tested, so evaluate the plugin in your own controlled environment.

Why might pnpm ask for build approval?

The upstream README warns that profile installation can encounter ERR_PNPM_IGNORED_BUILDS for dependencies including cloudflared, cpu-features, or ssh2. Review the requested package and its build consequences before allowing it.

Can I install the dsh-web-ui aggregate package instead?

Yes, upstream documents @linxin666/dsh-web-ui-all as an aggregate installer. This listing stays focused on one component so its features and risks remain clear; the aggregate can introduce additional packages and should be reviewed separately.