DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to track AI spend by model and project in one dashboard with Claude Unlimited

See cost and token use over time, split by model, project and account, on your own machine.

Who it is forA developer or team lead who needs to know which projects and models are driving AI usage costs.

The problemUsage data is spread across several accounts and providers, so it is hard to see where the spend goes.

The outcomeA local dashboard shows spend and tokens over time, broken down by model, project and account.

What you need first

  • Python 3.10+, git, and the claude CLI on your PATH
  • At least two accounts to pool: Claude Pro or Max, ChatGPT/Codex, or Anthropic API keys
  • A browser to complete the account login
  • macOS is the most tested platform; Windows and Linux are best-effort per the README

Steps

  1. Install the daemon and add your accounts as described in the README.
  2. Open the dashboard at http://127.0.0.1:4317/.
  3. Work in one or more projects with claude-unlimited code so requests are recorded.
  4. Open the Statistics view to compare spend and tokens by model, project and account.

Prompt for your agent

Using the DevDock-AI/claude-unlimited repo, run a short session with `claude-unlimited code` in <project-path>, then open http://127.0.0.1:4317/ and open the Statistics view. Expected output: charts of spend and tokens split by model, project and account. Verify that the project you used appears in the per-project breakdown.

Caveat. The README says the cost figures are estimates, so treat them as a guide rather than a bill.

Share: X LinkedIn Hacker News Email Copy link

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 [email protected] and we will look at it promptly. Full disclaimer page