No. TokenWatch runs entirely on your machine. It reads local files, calculates costs locally, and serves a dashboard only accessible at localhost:7842. Nothing is sent to any server.
The only external requests it makes are:
It reads the usage field from Claude Code’s JSONL session logs. Each assistant response contains:
input_tokensoutput_tokenscache_read_input_tokenscache_creation_input_tokensThese are multiplied by Anthropic’s current per-token prices (fetched automatically).
Not yet. TokenWatch currently reads Claude Code’s specific log format. Support for other tools is planned for a future version.
TokenWatch fetches live prices from LiteLLM’s community-maintained price list automatically on startup. When Anthropic changes prices, LiteLLM usually updates within hours. You can force a refresh by clicking ↺ Refresh in the prices panel.
Yes. Install it on each machine separately. Each instance reads that machine’s local Claude Code logs independently.
Copy ~/.claude/tokenwatch_config.json to the same path on the new machine.
Click ↺ Refresh in the prices panel to make sure you’re using current prices. Then visit http://localhost:7842/api/debug to verify the log format is being read correctly.
If numbers still seem wrong, email info@consulting-ai.tech with the output of the debug endpoint.
The Pro plan includes team cost aggregation (coming soon — currently in development). For now, each team member installs individually.
Yes — if TokenWatch doesn’t work for you, email info@consulting-ai.tech within 7 days of payment for a full refund, no questions asked.