codetime-dev/dsh-codetime
CodeTime for DeepSeek Harness
dsh-codetime is the native DeepSeek Harness telemetry backend for codetime.dev — the dsh-side sibling of codetime-cli's agent adapters for Claude Code / Codex / OpenCode / Pi. A SessionTelemetryCoordinator drives emit(record) for every projected session event and translates each one into a codetime canonical event (session.started, turn.started, prompt.submitted, tool.started/completed, file.changed, model.usage, …). Events accumulate per session, are rolled up in 15-minute buckets (per-model / per-tool / per-file / per-turn aggregates) with the exact wire format codetime-cli uses, and a periodic flush POSTs { rollups, replace: true } to /v3/agent/ingest so dsh activity lands on the same dashboard as your other AI-agent tools. emit only queues in memory (no I/O), so it never blocks the session firehose; batching, the periodic timer and a bounded shutdown drain own the network.
Install
dsh plugin --profile web add dsh-codetimenpm dsh-codetime 0.1.1 verified 2026-09-03 (repository field → github.com/codetime-dev/dsh-codetime; README EN primary). One-command install: dsh plugin --profile web add dsh-codetime.
Compatibility
DSH web profile with the built-in session-telemetry seam (@deepseek-ai/dsh-session-telemetry); a codetime.dev account and the codetime-cli ingest endpoint.
Details
- Repo: codetime-dev/dsh-codetime
- Category: Coding & Development
- Stars: 0
- Version: npm dsh-codetime 0.1.1
- Last push: 2026-08-14
- First seen: 2026-08-14
Recent updates
0.1.1 is the current npm release (verified 2026-09-03); no changelog section in README beyond the telemetry mapping table.
FAQ
- What data does it send?
- Session, turn, tool, file and model activity events (rollups in 15-minute buckets), projected through dsh's session-telemetry redaction waterfall before they leave the host.
- Does it need the codetime CLI?
- No — it is a standalone backend speaking the same /v3/agent/ingest wire format the CLI uses, but you still need a codetime.dev account/dashboard to receive the data.
- Can it slow the agent down?
- No — emit() only queues records in memory; all network work happens in a periodic flusher and a bounded shutdown drain.
Alternatives
H1a3x/dsh-token-stats · YZz-S/dsh-token-cost-meter