dsh-plugin-wakatime
跟踪您在 DeepSeek Harness 中使用 AI 编码的时间，并将其作为 AI 编码活动报告给 WakaTime。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:Dynesshely/dsh-plugin-wakatime#9eacaec72a91ab37c242434c2c72f42e835ce1aePlugin Wakatime 以 dsh-plugin-wakatime 发布，当前版本为 0.2.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
dsh-plugin-wakatime — WakaTime heartbeats for DeepSeek Harness
A DeepSeek Harness (DSH) Host plugin that reports the time you spend coding with AI inside DSH to WakaTime, as category: "ai coding" heartbeats, so it shows up in your AI Coding stats next to everything else you track.
It does not fake per-file keystroke heartbeats. It answers one question — was this stretch of time spent working on this project with an AI pair? — and it does so in the background, without blocking the host. Since v0.2 it also ships a Usage page inside DSH.
entity is the session's working directory, project is its folder name, so AI time is broken down per project in WakaTime.api_key means one warning in the log and an inert plugin; DSH starts normally.The bundle needs its own dependency first: install_bundle symlinks a local directory and does not install what the bundle depends on.
git clone git@github.com:Dynesshely/dsh-plugin-wakatime.git
cd dsh-plugin-wakatime
pnpm install # or npm install
Then install the repository root as a bundle from DSH's Plugin Manager:
plugin_manager → install_bundle → D:\Projects\Dynesshely\dsh-plugin-wakatime
Restart DSH after installing or upgrading — the Host code lives in the server process, so refreshing the page is not enough. Remove it with remove_bundle (package name dsh-plugin-wakatime).
Prerequisite: an api_key under [settings] in ~/.wakatime.cfg — the same file your other WakaTime clients already use. Its proxy, hostname, and debug values are reused.
Config lives on the plugin's row (config in cordis.patch.yml, or the form in Settings). Precedence: plugin config > ~/.wakatime.cfg > built-in defaults.
| Key | Default | Purpose |
|---|---|---|
enabled | true | Master switch. |
minIntervalSeconds | 120 | Minimum gap between heartbeats, all sessions combined. |
idleTimeoutMinutes | 15 | Gap that ends the current timing stretch. |
entityType | 'file' | file reports the project path; app reports DeepSeek Harness. |
includeSubagentSessions | false | Count subagent sessions separately (off: the same wall-clock time is not counted twice). |
category | 'ai coding' | WakaTime activity category. |
apiKey | empty | Overrides the api_key from ~/.wakatime.cfg. |
debug | false | Verbose diagnostics in the log file. |
An empty string means "fall back", not "set it empty". The remaining keys — apiUrl, proxy, hostname, language, userAgent, projectFromCwd — and the exact semantics of all of them are in docs/design.md.
v0.2 adds a Usage page: a sidebar entry sitting next to Plugins, Automation tasks and Context insights. It is fed by the Host route GET /wakatime/usage.json (Cache-Control: no-store), so everything shown is real data from this machine.
| Block | Shows |
|---|---|
| Local time | today (large), this week, all-time |
| Today's volume | input / output tokens, characters typed, sessions, heartbeats |
| Last 7 days | inline SVG bar chart, one bar per day |
| Projects | top 5 by tracked time |
| WakaTime | whether api_key is configured, hostname, today's remote AI Coding time, pending queue size, last send, last error |
Page copy is bilingual and follows DSH's language setting (en / zh), and the page is drawn with the host's theme variables, so it matches light and dark. The remote figure is derived from your heartbeats (GET /users/current/heartbeats?date=…, AI Coding categories only, 60 s cache); if that one request fails, only that block reports an error and the local stats keep working. A refresh button re-fetches the JSON.
session/event → accumulate activity + token/char deltas → throttle (≥ minIntervalSeconds)
├── ok → WakaTime: single beat, or .bulk (≤ 25 per batch)
└── fail → local queue → backoff replay
user/message, assistant/message (with usage), tool/call, tool/result, turn/start, turn/end; running turns stay alive thanks to a 15 s tick.Authorization: Basic base64(api_key) against the WakaTime API v1. Each beat also feeds a local per-day store (usage.json, 30 days) that backs the Usage page.<DSH_HOME>/cache/wakatime-dsh/wakatime.log (or ~/.dsh/cache/… when DSH_HOME is unset). The offline queue and state live in the same directory.Sent to WakaTime: project working-directory path, project name, DSH session id, input/output token counts, characters typed, timestamps, plus language and hostname when configured.
Never sent: code, prompt text, model output, file contents, terminal output. The plugin works on event metadata, never on the text itself. The usage store stays on your disk.
No build step, plain ESM. lib/*.js is testable without DSH:
pnpm install
node --test
index.js Host entry: Config + apply(ctx, config)
lib/tracker.js session/event → activity state → heartbeat scheduling
lib/usage.js per-day aggregation behind the Usage page
lib/client.js WakaTime HTTP client (auth, batching, retry, proxy fallback)
lib/heartbeat.js heartbeat builder (pure)
lib/cfg.js ~/.wakatime.cfg + plugin config merge
lib/queue.js persistent offline queue (atomic writes)
test/ node:test suites
MIT © 2026 Dynesshely