{
 "schema_version": 1,
 "generated": "2026-10-24",
 "id": "aisland-sjl-dsh-usage--compare-dsh-and-claude-code-token-share",
 "repo": "Aisland-SJL/dsh-usage",
 "repo_url": "https://github.com/Aisland-SJL/dsh-usage",
 "repo_slug": "aisland-sjl-dsh-usage",
 "title": "See how tokens split between DSH and Claude Code",
 "page_title": "How to see how tokens split between DSH and Claude Code with DSH Usage",
 "summary": "Use the channel share widget to compare DSH and Claude Code token use from local logs.",
 "who": "A developer who uses both DeepSeek Harness and Claude Code and wants to know where their token budget actually goes.",
 "problem": "Token use is spread across two tools, so there is no single view of which channel is doing most of the work.",
 "outcome": "A channel share bar shows the ratio of DSH to Claude Code usage, built from aggregated numbers in ~/.claude/projects without sending message text anywhere.",
 "steps": [
  "Install the plugin into the Web profile with `dsh plugin --profile web add \"github:Aisland-SJL/dsh-usage\"`.",
  "Fully restart `dsh web` and hard-refresh the browser so the aggregation starts.",
  "Open the detail panel and read the Channel share widget for the DSH versus Claude Code ratio.",
  "Open the Usage log widget to drill into per-day and per-model detail for each period.",
  "If the totals look wrong, check the coverage status in the usage response, since partial or unavailable coverage is labeled in the UI. (inferred, check the README)"
 ],
 "agent_prompt": "In the repo Aisland-SJL/dsh-usage, open the Channel share widget in the dsh web panel at <dsh web URL> and report the DSH and Claude Code shares. Verify that the coverage state is shown as complete, partial, or unavailable before you trust the ratio.",
 "agents": [
  "any"
 ],
 "difficulty": "Intermediate",
 "time": "30 minutes",
 "basis": "readme",
 "caveat": "Claude Code totals depend on the logs under ~/.claude/projects, and the README says unsupported historical formats are not repaired, so some sessions may be skipped.",
 "category": "Data and analytics",
 "tags": [
  "Data and analytics"
 ],
 "lang": "javascript",
 "requirements": [
  "DeepSeek Harness host, version 0.2.0-rc.2 for v0.3.1 of this plugin, with the dsh CLI installed",
  "An API key for each provider you want to query, configured through Harness credentials (for example DEEPSEEK_API_KEY)",
  "Node.js and npm only if you plan to run the offline tests or develop the plugin"
 ],
 "risk": "sensitive",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.9,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/aisland-sjl-dsh-usage/compare-dsh-and-claude-code-token-share/",
 "md": "https://dedupedai.com/use-cases/aisland-sjl-dsh-usage/compare-dsh-and-claude-code-token-share/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/aisland-sjl-dsh-usage--compare-dsh-and-claude-code-token-share.json",
 "api_version": "v1"
}