You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(adapter): add DeepSeek Harness (dsh) usage support #1647
Please add a first-class usage adapter for DeepSeek Harness (dsh).
Current behavior
I tested ccusage 20.0.20. It supports several coding-agent sources, but there is no dsh subcommand or DSH source in the unified report. ccusage dsh ... returns Unknown command 'dsh'.
Data source
DSH persists sessions as zstd-compressed JSONL under:
Support daily, monthly, session, and unified reports
Include provider/model breakdowns and configurable path discovery
Preserve the existing pricing override mechanism
Accounting detail
DSH can persist streaming assistant/chunk usage and a finalized assistant/message usage record for the same turn/step. The adapter should deduplicate or prefer the finalized record so streaming updates are not double-counted.
I can provide a sanitized fixture if useful. No prompts, credentials, or private session content are required for the adapter test fixture.
This issue was auto-closed. Issues from new contributors are auto-closed by default.
Maintainers review auto-closed issues and reopen worthwhile ones. Issues that do not meet the quality bar in CONTRIBUTING.md may not be reopened or receive a reply.
Keep the issue short, concrete, and written in your own voice.
If a maintainer replies lgtmi, your future issues will stay open. If a maintainer replies lgtm, your future issues and PRs will stay open.
It adds DSH raw and concatenated zstd session-log discovery, one usage row per turn and step with finalized-message replacement, provider/model attribution, pricing lookup, focused dsh reports, unified-report wiring, config schema support, docs, and fixture tests.
The Rust workspace formatter, clippy, and tests pass locally. If this direction is useful, please reply lgtm so I can open the PR under the contributor gate.
Historical audit: this discussion was auto-closed by the legacy contributor gate. That closure did not assess technical importance.
Audit result: excluded from the current maintenance scope. This request depends on an unsupported external source, unavailable schema or fixture, platform or release infrastructure the project cannot reliably maintain, an operational service, or an unsafe or underspecified design. It is not a candidate for automatic reopening or implementation.
Activity
pullfrog commentedon Aug 27, 2026
github-actions commentedon Aug 27, 2026
This issue was auto-closed. Issues from new contributors are auto-closed by default.
Maintainers review auto-closed issues and reopen worthwhile ones. Issues that do not meet the quality bar in CONTRIBUTING.md may not be reopened or receive a reply.
Keep the issue short, concrete, and written in your own voice.
If a maintainer replies
lgtmi, your future issues will stay open. If a maintainer replieslgtm, your future issues and PRs will stay open.See CONTRIBUTING.md.
oksure commentedon Aug 27, 2026
I prepared a focused implementation on my fork:
https://github.com/oksure/ccusage/tree/contrib/dsh-usage-adapter
It adds DSH raw and concatenated zstd session-log discovery, one usage row per turn and step with finalized-message replacement, provider/model attribution, pricing lookup, focused dsh reports, unified-report wiring, config schema support, docs, and fixture tests.
The Rust workspace formatter, clippy, and tests pass locally. If this direction is useful, please reply
lgtmso I can open the PR under the contributor gate.ryoppippi commentedon Aug 31, 2026
Historical audit: this discussion was auto-closed by the legacy contributor gate. That closure did not assess technical importance.
Audit result: excluded from the current maintenance scope. This request depends on an unsupported external source, unavailable schema or fixture, platform or release infrastructure the project cannot reliably maintain, an operational service, or an unsafe or underspecified design. It is not a candidate for automatic reopening or implementation.