Question 1

Does Pulse Code read my prompts or my code?

Accepted Answer

No. The agent sends token counts, model names, tool names, timestamps and the size of each tool result. It never sends your prompts, Claude's replies, your file contents, your tool arguments, or what your tools returned. It opens every transcript read-only and writes nothing inside your Claude Code directory.

Question 2

What are cache read and cache write tokens?

Accepted Answer

Claude Code re-sends your conversation on every turn. Rather than charge full price each time, Anthropic caches it: the first send is a cache write, and every later turn that reuses it is a cache read. Cache reads are much cheaper than fresh input. On a real machine we measured, 97% of all tokens were cache reads — which is why one combined token number tells you almost nothing.

Question 3

How many tokens does Claude Code actually use per session?

Accepted Answer

Far more than most people expect, because every turn re-sends the whole conversation. A long session can pass a billion tokens, most of them cache reads. Pulse Code shows the per-session total split into four buckets — input, output, cache write and cache read — so you can see where it went instead of guessing.

Question 4

Which MCP server is using the most of my tokens?

Accepted Answer

The MCP page ranks every server by the estimated context cost of its tool results, and ranks individual tools by cost per call. A chatty server is worse than it looks: whatever it returns goes into your context, and every later turn in that session re-sends it. One fat result is paid for many times over.

Question 5

How do I track Claude Code costs across multiple machines?

Accepted Answer

Install the agent on each machine with the same API key. Every machine reports to one account, and each session is tagged with the machine it ran on. You can filter any view by machine, or see the whole fleet together.

Question 6

Can I monitor scheduled Claude Code cron jobs?

Accepted Answer

Yes. Claude Code marks headless runs itself, so scheduled work is separated from interactive work automatically. To attach a job name, wrap the command with cc-run: cc-run --job "nightly-audit" -- claude -p "...". The job name then appears on every cost breakdown.

Question 7

Why is my Claude Code context so expensive?

Accepted Answer

Usually because something large went into it early and never left. A big file read, a verbose tool result, or a chatty MCP server all stay in context for the rest of the session and are re-sent on every turn. The session detail view has a context growth chart that makes this visible: a line that climbs and never comes down is the thing worth fixing.

Question 8

Is there a free tier?

Accepted Answer

Yes. One machine and seven days of history, free, with no card required. Pro is $9 a month for five machines, a year of history, alerts and digests. Team is $29 for unlimited machines and two years of history.

Question 9

How is this different from Claude Pulse?

Accepted Answer

Claude Pulse is a Chrome extension that tracks your usage on claude.ai, the website. Pulse Code tracks Claude Code, the command-line tool. Same people, same approach to privacy, different surface. Many people use both.

Sign in