Chaching!

Quietly setting
money on fire.

A local cash register for your coding agents.

Node 24.16+ Runs locally. No chaching signup. No telemetry.

A Chaching receipt itemising coding-agent spend and cache discounts from fictional usage.

Same engine. Two ways to watch it burn.

Terminal people.
The terminal dashboard showing spend by model, cache savings and keyboard controls.
Browser people.
The Chaching dashboard with spend over time, account quotas and recent sessions, using the same fictional data as the terminal.

Actual product. Fictional developer. All too plausible damage.

One register for your coding agents.

The damage.
And the discount.

It counts the cache hits too. See what your agents spent, what caching saved, and which model picked up the tab.

Print a shareable receipt or monthly recap. Open Wrapped in the dashboard for your year in tokens. A paper trail for your questionable life choices.

chaching receipt --png --redactchaching wrapped --png --redact
See a yearly Wrapped
Meet the commands
A monthly Wrapped recap generated from the same fictional usage as the receipt and dashboard.
Your month in tokens. Ready to overshare.

Several machines.
One reckoning.

The laptop. The desktop. The agent you forgot you left running. Optional sync brings their aggregates into one view through your own PostgreSQL database.

Keep track of your Accounts and subscription fees. With local Tokenmaxx data, see available account quotas alongside the spend.

Set up multi-machine sync

Your data stays
your business.

Runs locally.
No chaching signup.
No telemetry.

Local tools are read on your machine. Cursor's Admin API and PostgreSQL sync connect only when you configure them. Tokenmaxx integration reads its local SQLite database.

Read the configuration docs

The only thing it phones
is your conscience.

Requires Node 24.16 or newer. Start here.