{
  "id": 12195234,
  "title": "I wanted to know which project was eating my Claude Code quota",
  "url": "https://urgent.news/2026/10/05/i-wanted-to-know-which-project-was-eating-my-claude-code-quota",
  "topic": "ai",
  "section": "AI",
  "published": "2026-10-05T17:10:37.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/rosehsu47/i-wanted-to-know-which-project-was-eating-my-claude-code-quota-5e7k"
  },
  "original_language": "en",
  "account": "I interviewed a user who sought to understand which project was consuming their Claude Code quota. The user discovered that Claude Code's native usage tracking did not provide the necessary breakdown, showing only account-wide percentages and vague tags. Determined to gain detailed insights, the user developed a plugin called \"quota-audit\" to analyze the per-message token usage data stored in each local session under ~/.claude/projects/*/*.jsonl. This plugin meticulously breaks down usage by project and skill, marking the exact moments when rate limits were breached and identifying the repositories that were throttled. The report generated by the plugin details financial estimates, highlighting which projects and skills dominate the usage, and even flags sessions that cross the 150,000 context threshold, which typically represent significant cost drivers. It also helps identify any potential polling loops that may appear to inflate session counts without actually using quota. The user can access this tool within Claude Code either through the plugin marketplace or by running the claude plugin command. The report offers detailed insights into the quota consumption, but it's important to note that the dollar figures are estimates and not the actual bill, and the plugin can only view data from the machine it's running on, not from other devices or platforms. The developer of the plugin, Rosehsu47, encourages users to explore how they can optimize their usage of Claude Code based on these valuable insights.",
  "summary": "When I hit my Claude Code 5-hour or weekly limit, I want to know which project used it up. /usage doesn't answer that. It gives account-wide percentages plus a few tags like \">150k context\" or \"4+ parallel sessions\". Nothing is broken down per project, and I can't check those percentages against anything. Claude Code already writes per-message token usage into every local session transcript under…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 3,
    "also_reported_by": [
      {
        "outlet": "Dev.to",
        "title": "I wrote a safety mod that crashes on purpose. Claude Code ran the command anyway.",
        "url": "https://urgent.news/2026/10/05/i-wrote-a-safety-mod-that-crashes-on-purpose-claude-code-ran-the",
        "published": "2026-10-05T16:37:28.000Z"
      },
      {
        "outlet": "AWS Machine Learning",
        "title": "Supercharge regulated workloads with Claude Code and Amazon Bedrock",
        "url": "https://urgent.news/2026/10/05/supercharge-regulated-workloads-with-claude-code-and-amazon-bedrock",
        "published": "2026-10-05T17:25:20.000Z"
      }
    ]
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}