Version 0.0.6 with Claude Code support

See which repos use your AI coding tokens.

RepoSpend is a local first dashboard for tracking Codex and Claude Code token usage, repo by repo. It reads files already on your disk. No login, no telemetry, no prompt uploads.

$npx repospend

View on GitHub

85weekly npm downloads5GitHub stars0.0.6latest npm versionNode 20+runtime

repospend → localhost:2005

Overview

Your local AI coding activity at a glance

Total tokens15.9m

API equivalent cost$84.83

Top repoone-ring

AI providersSources scanned: Codex, Claude Code

AllCodexClaude Code

The dashboard

Your local AI coding activity at a glance.

One screen for every signal that matters: spend, top repos, cache reuse, command issue rate, and file edits. All grouped by Git root, all running on localhost.

localhost:2005 RepoSpend v0.0.6

What it shows

Six signals that explain local usage.

No vanity metrics. Just the things that tell you, repo by repo and session by session, where tokens and cost went.

Repo cost

Walks sessions to their Git root, so apps, packages, and scripts roll up into the project you recognize.

Git rootaggregation

Session inspector

The shape of every run: cost, model, file edits, commands, highlights, warnings, and what made that session expensive.

details

Agent friction

Separates blocking command failures from harmless shell exits, so high-token troubleshooting loops are easier to triage.

signals

Token shape

Input, output, cached input, and reasoning tokens are shown separately, with cache reuse treated as a core metric.

tokenscache

By model, day, and hour

Compare Codex and Claude Code locally. Slice by model, day, hour, source, app, repo, and session outcome.

compare

Export anywhere

JSON and CSV exports keep the data useful outside the dashboard: spreadsheets, notebooks, shell scripts, or your own tools.

jsoncsvcli

Screenshots

Every screen, explained.

Click through the real product views. Expand a screenshot when you want to inspect the details without opening the app.

How it works

Three steps. About twelve seconds.

No login, no API keys, no setup wizard. The hardest part is finding your terminal.

Run it

One command, and your dashboard opens at localhost:2005.

$ npx repospend

Read your files

Scans ~/.codex and ~/.claude in read only mode, then walks sessions to Git roots.

reads ~/.codex and ~/.claude

Review usage

Find the repo using the most tokens and inspect why.

localhost:2005

Privacy by design

Your prompts never leave your laptop.

RepoSpend binds to localhost. There is no hosted analytics service and no account to create. It is Apache 2.0 and auditable.

Read the source Security policy

No login

No account because there is nothing to store.

No telemetry

The dashboard does not report usage back.

No uploads

Prompt and tool output stay local.

No edits

Codex and Claude files are read only.

Supported tools

Reads what is already on disk.

RepoSpend was built first for Codex. Claude Code support is newer and depends on what your local files include. RTK appears when local RTK data exists.

Codex

full support

Tokens, models, sessions, repo grouping, command friction, file edits, and cost. Reads ~/.codex/state_5.sqlite and ~/.codex/sessions.

Claude Code

initial

Sessions, projects, models, timestamps, and tokens when available. Unknown token/cost fields stay unknown instead of guessed.

RTK

optional

Surfaces RTK token savings analytics only when local RTK data exists. Otherwise it stays out of the way.

Commands

Most people just type repospend.

Power users get terminal friendly commands and source filters. The full help is one --help away.

~ repospend --help

$repospend

Open the dashboard at localhost:2005

$repospend scan

Scan local Codex and Claude Code files again

$repospend by-repo

Aggregate tokens and cost by Git root

$repospend by-day

Daily timeline of token use and spend

$repospend by-hour

Hourly distribution for spotting unusual bursts

$repospend by-model

Split usage across model names

$repospend by-app

Group by app or surface where detectable

$repospend export --format json

Dump the local usage data as JSON

$repospend export --format csv

Export CSV for a spreadsheet

$repospend by-repo --source codex

Filter aggregates to one source

$REPOSPEND_NO_OPEN=1 repospend

Print the URL without opening a browser

FAQ

Reasonable questions, honest answers.

Trust the dashboard before you install it. These are the things people ask first.

Does RepoSpend send my prompts anywhere?

No. RepoSpend binds to localhost and reads files already on your machine. There is no login, no telemetry, and no prompt upload path in the dashboard.

Is the cost number my actual bill?

No. RepoSpend shows API equivalent cost estimates from local token counts and pricing rules. It is useful for comparing repos and sessions, but it is not an invoice.

Does it edit Codex or Claude files?

No. Codex, Claude Code, and RTK data are read only. RepoSpend settings live under ~/.repospend and can be reset from the Settings page.

Can I run it without npx?

Yes. Install once with npm install -g repospend, then run repospend. Node.js 20 or newer is required.

Find out where it all went.

One command. No account, no upload, no surprise. The dashboard is already on your machine; RepoSpend just turns it into a map.

$npx repospend

Star on GitHub