DeepSeek Harness plugin

dsh-token-dashboard

DSH web GUI token-consumption heatmap: a daily/weekly total-token usage panel fed by session-log usage events

Jump to install

Source facts

Repository
apodemakeles/dsh-token-dashboard
Latest update
Aug 16, 2026
Category
Development & Runtime
GitHub stars
2
Format
plugin
Catalog evidence
Upstream dsh.bundle evidence
Evidence path
package.json#dsh.bundle
Checked against
0.1.0-rc.8
Upstream check date
2026-08-20

This evidence comes from the upstream catalog. This site has not installed, run, or security-reviewed the plugin.

Install

Start with a prompt that asks an agent to review the GitHub repository and source. Switch to the command if you want to install it yourself.

Copy this prompt into DSH, Codex, or another agent and ask it to review the GitHub repository and source first.

Do not install or run any commands yet. Read this plugin's GitHub repository, README, and relevant source code. Then answer the questions below clearly and directly so I can decide whether it fits my needs:

1. What is this plugin, and what problem does it solve?
2. Who is it for, and what are its typical use cases?
3. How is it used after installation? Include one minimal example.
4. What known limitations or privacy, security, compatibility, or maintenance risks does it have?
5. Give a clear recommendation: recommend, conditionally recommend, or do not recommend, with reasons.

Distinguish statements documented by the repository, inferences from source code, and unknowns. If evidence is insufficient, say so explicitly. Do not guess or simply repeat the README.

GitHub: https://github.com/apodemakeles/dsh-token-dashboard
Plugin: dsh-token-dashboard
Author: apodemakeles

Check the source files

Read the README and other files from this plugin directory before installing.

File explorer4 files
README.mdSource · read only
README language

@apodemakeles/dsh-token-dashboard

English | 中文

A DeepSeek Harness (DSH) web GUI plugin: a token-consumption heatmap panel. It shows your total token usage per day / per week across all projects on this machine, GitHub-contributions style. Usage facts are projected into a local SQLite database by a persistent Worker, so opening the panel never scans session logs.

> Status: released v0.2.0 — GitHub distribution is live. The package is not currently published to npm.

Screenshots

Weekly heatmap

![Weekly token-usage heatmap](docs/images/token-dashboard-weekly.png)

Daily view

![Daily token-usage bar chart](docs/images/token-dashboard-daily.png)

What it does

  • Host half — listens to live session/event, flushes through DSH's durability barrier, and sends minimal usage deltas to a persistent Worker. The Worker owns SQLite (node:sqlite), commits facts/checkpoints atomically, and serves one consistent snapshot endpoint.
  • Client half — registers a Token entry in the sidebar and opens a dedicated panel rendering the heatmap (weekly grid + daily view). It fetches a single GET /api/token-dashboard/snapshot per open/refresh/page change.
  • CLIdsh-token-dashboard status|verify|rebuild|backups|restore|cleanup for local maintenance.

Installation

From GitHub:

dsh plugin --profile web add github:apodemakeles/dsh-token-dashboard

Then restart dsh web. Open any project session and click the Token entry in the sidebar.

The npm package is not currently published; use the GitHub installation above.

Data and operations

  • Projection database: $DSH_HOME/data/token-dashboard/usage-v1.sqlite (default ~/.dsh).
  • Total tokens = inputTokens + outputTokens + cacheReadTokens (cache reads count into the headline).
  • The panel only calls the snapshot route; it does not trigger listSnapshots, inspect, readFrom, flush, or backfill.
  • First startup initializes the database in the background; the panel shows phase/progress until ready.

Development

git clone https://github.com/apodemakeles/dsh-token-dashboard.git
cd dsh-token-dashboard
pnpm install && pnpm build
dsh plugin --profile web add link:$(pwd)

See [.scratch/dsh-token-dashboard/map.md](.scratch/dsh-token-dashboard/map.md) for the project map (planning tracker), [docs/durable-usage-architecture.md](docs/durable-usage-architecture.md) for the architecture contract, and [docs/dev-loop.md](docs/dev-loop.md) for the full dev loop.

Known limitations

  • Projection is machine-local: it reads sessions stored on this machine (~/.dsh/sessions is the authority; SQLite is a rebuildable projection).
  • Host/Worker changes require restarting DSH; client HMR does not cover the persistent Worker.
  • SQLite is experimental in Node 24 (node:sqlite); the plugin checks capability at startup and does not hide the warning globally.

License

MIT