dsh-web
zhu1090093659/dsh-webDeepSeek Harness(DSH)Web 插件聚合生态包 · 一切皆插件,创意工坊分发(dsh-market.com)
English | 中文 | 日本語 | 한국어 | Español | Português
Local token & cost dashboard for AI coding tools
Try it without installing → tokdash.github.io/demo
[!NOTE]
Multiple machines, one dashboard. Add the Tokdash instances running on WSL, a Mac, or any other box in Settings: every view combines whatever you select, the Servers tab compares the machines side by side, and the Quota tab keeps each provider's window bars and reset countdowns grouped per machine. Remote access → · quota tracking →
Also from the same author: Cosyncing. Synchronize and control your agents — from CLI to GUI, from desktop to phone. Cosyncing keeps your coding agents in sync across your own network.
pipx install tokdash
tokdash setupThat's it. tokdash setup detects the runtime, installs a managed one if needed, registers a local service, and prints the dashboard URL — http://127.0.0.1:55423. Full options, first-run notes, and updates live in Install & run; prefer to look around first? The live demo runs on the real UI.
One local package, one local data index — and four ways to read it. Every surface parses the same session logs on your own machine, so the browser dashboard, the terminal, the menu bar, and your agent's statusline always agree.
View · What it is · Reach for it when WebUI · The full dashboard: Overview, Sessions, Stats, Report, Quota, Servers · You want the whole picture, charts, and drill-down TUI · tokdash tui — Overview, Report and Quota in the terminal · You live in the terminal and want the numbers without a browser Companion · Native menu-bar (macOS) / notification-area (Windows) app · You want today's spend and quota visible all day, dashboard closed Statusline · A live token/cost item inside your agent's statusline · You want the cost ticker exactly where you type
The dashboard is a single page served by the local FastAPI app: exact input / cache / output token breakdowns, per-tool and per-model tables, a contribution heatmap, a week/month/year Report, per-provider Quota windows with reset countdowns, and a Servers tab that combines and compares several machines. Click any screenshot to open the live demo.
Overview Usage Report Quota tracking Multiple servers, one total
Prefer to stay in the terminal? tokdash tui opens the Overview, Report, and Quota tabs without a browser, reading the same local index (and the shared on-disk database when a tokdash serve is running beside it).
TUI — Overview TUI — Quota
tokdash tuiKeyboard
Key · Action q · Quit r · Refresh the current tab 1 / 2 / 3 · Switch to Overview / Report / Quota t w m y a · Jump to a period directly (both period tabs; t/a are Overview-only) p · Next time window (forward-only cycle) [ / ] · Step one whole calendar period back / forward — never into the future 0 · Back to today u · Poll quota (Quota tab only) ? · Help overlay with all keys
One-shot report CLI
For a one-shot report you can pipe or script:
tokdash report --period weekThe period is a flag, not a positional argument. Accepted values: today (the default), week, month, year, all, a number of days, or Nd/Nw/Nm/Ny shorthand; week, month and year are the same calendar-aligned windows the web Report tab shows. tokdash report also accepts --json, --pretty and --output , following the same conventions as tokdash export.
An optional native menu-bar app for macOS and notification-area app for Windows: a compact, read-only view of the Tokdash service without the dashboard open.
macOS menu bar Windows notification area
Windows — Microsoft Store (recommended, signed by Microsoft, requires Windows 11):
Direct download — the latest companion release: a universal DMG (arm64 + x86_64, macOS 14+) and a self-contained portable ZIP (x64, Windows 11; Windows on Arm via x64 emulation).
What it shows, and how setup works
Setup: run Tokdash 1.5.2 or newer (Install & run), install the companion, and it connects to http://127.0.0.1:55423 by default — its settings let you add, test, name, or remove explicit endpoints, including private Tailscale Serve URLs. The companion only contacts the endpoints you configure; low-quota notifications and launch at login are opt-in.
[!WARNING]
The GitHub Releases binaries are unsigned. macOS Gatekeeper and Windows
SmartScreen will show an unknown-publisher warning. Download only from this
repository, verify the included SHA256SUMS, and continue only if you trustthe release. The Microsoft Store build is signed by Microsoft and is not
affected; macOS signing and notarization are planned for a later release.
Checksum, update, and removal instructions live in the companion release guide.
The local API can power a statusline item in your coding agent showing live token/cost stats:
Ready-made templates (bash and PowerShell), install/config, and the endpoint reference live in `docs/guides/statusline/`.
Prerequisites: Python 3.10+ and one or more supported clients.
Recommended isolated install:
pipx install tokdashIf you do not use pipx:
python3 -m pip install --user tokdashRun the onboarding wizard:
tokdash setupThe wizard configures a reversible user-level background service when the platform supports one, then prints the dashboard URL (default: http://127.0.0.1:55423). If no supported service manager is available, it records setup state and prints foreground run guidance. It uses localhost-first defaults, does not require sudo for the local service, and keeps your usage history unless you later uninstall with --purge.
For a non-interactive setup from an agent, script, or bundle, run tokdash setup --auto --json; to preview what setup would change, tokdash setup --dry-run. To expose the dashboard explicitly on all network interfaces with writes disabled, run tokdash setup --bind 0.0.0.0; review the remote-access guide first.
Then check the install:
tokdash doctordoctor checks the runtime, background service, configured port, data paths, and update-check status. Use tokdash doctor --json for automation.
tokdash update # upgrade the managed runtime and restart the service when possible
tokdash uninstall # reverse exactly what setup created; keeps usage history by defaultupdate only drives install methods Tokdash can safely manage. If your runtime was installed by a package manager Tokdash does not own, it prints the exact manual guidance instead of mutating that environment.
Existing installs: migration from before v1.0
If you installed Tokdash before the onboarding flow, upgrade first:
pipx upgrade tokdash
# or: python3 -m pip install --user -U tokdashThen run tokdash doctor and tokdash setup when you want Tokdash to manage the background service. If you already have a hand-written systemd or launchd service, setup does not silently replace it: it refuses unmarked tokdash.service / plist files by default. Keep managing that service yourself, remove it before setup, or run tokdash setup --force after checking tokdash setup --dry-run. --force also handles pre-1.0 services that already occupy port 55423 but do not expose the new /health fingerprint: it rewrites and restarts the existing tokdash.service. Use tokdash setup --no-service to skip service creation.
If your current setup uses a conda/system/user-pip interpreter and you want tokdash update to manage future upgrades, migrate the service to Tokdash's setup-owned venv:
# Upgrade the tokdash command you are about to run, for example:
python3 -m pip install --user -U tokdash
# or, for a conda base install:
conda run -n base python -m pip install -U tokdash
tokdash setup --runtime venv --force
tokdash doctorThis keeps your usage history under ~/.tokdash, rewrites the user service to run ~/.tokdash/runtime/python-venv/bin/python -m tokdash, and lets future tokdash update upgrade that managed venv and restart the service. If you installed with pipx, you can instead keep the pipx runtime and upgrade with tokdash update or pipx upgrade tokdash.
If you only want a one-off foreground process:
tokdash serveOpen http://127.0.0.1:55423. Use tokdash serve --port if the default port is busy. By default tokdash serve opens the dashboard in your browser once on startup; pass --no-open to disable it. A bare tokdash with no command just prints the command help and exits — it no longer starts tokdash serve behind your back.
For full onboarding details — runtime choices, WSL/systemd behavior, macOS launchd, Tailscale, bundling, update checks, and safe uninstall semantics — see `docs/guides/ONBOARDING.md`. For remote access through Tailscale Serve, SSH forwarding, or an explicit network bind, see `docs/guides/REMOTE_ACCESS.md`.
tokdash tui — Overview, Report and Quota in the terminal, no browser required