vibeinging/dsh-trace

DeepSeek Harness telemetry backend that exports turns, model steps, and tool calls to yiTrace over HTTP.

A telemetry backend plugin that exports turns, model steps and spans — each completed turn is stored under DSH_TRACE_DATA_DIR, and shutdown closes unfinished spans and flushes the database. Its bundled dsh.bundle.patch disables the telemetry-otel row, loads dsh-trace from DSH_TRACE_DATA_DIR and loads an invariant companion (dsh-trace-invariant); the same command with --profile headless enables the independent headless profile. The README documents verification: after install, a profile dump must show telemetry-otel disabled and both dsh-trace and dsh-trace-invariant present. It deliberately ships no viewer and no built-in redaction rules — inspection is left to yiTrace-compatible local tools or the @yitrace/db query API against the configured data directory.

Other ★ 2 updated 2026-08-12 ✅ runtime-tested
View on GitHub ↗

Install

⚠️ Install command not yet confirmed — check the README on GitHub for the exact command.

Compatibility

A compatible DSH web or headless profile that provides Session Telemetry and the invariant service (README prerequisites). Installation additionally requires authorized GitHub access, pnpm 11.7.0, and the private @deepseek-ai/* scope authenticated through NPM_TOKEN.

Details

Recent updates

The README documents prerequisites, the private-install requirements, the bundle patch behaviour and the verification steps rather than a versioned changelog; there is no release history or migration section and no registry release. Verify the current install instructions in the repository before installing.

FAQ

How do I install dsh-trace?
It is a private Git distribution: the README documents dsh plugin --profile web add -w github:dsh-external/dsh-trace#<reviewed-commit> and states installation requires authorized GitHub access, pnpm 11.7.0, a reviewed commit and a compatible DSH profile — so treat the command as a template and confirm access first.
Does it replace OpenTelemetry?
Its bundle patch disables the telemetry-otel row and loads dsh-trace plus its invariant companion instead; the README says a profile dump must show telemetry-otel disabled after install.
Where is the data and how do I view it?
Turns are stored under DSH_TRACE_DATA_DIR (shutdown flushes unfinished spans). The README notes there is no viewer and no built-in redaction — use yiTrace-compatible local tools or the @yitrace/db query API.

Alternatives

Ychris12138/dsh-usage-stats · LeemanCheung/dsh-token-usage · xiufengsun/TokenTracker

More plugins in Other

Browse more in Other

Guides for Other plugins