How to track what you spend on AI coding agents

To know what you really spend on AI coding agents, you have to add up three numbers that live in different places: flat subscriptions such as Claude Pro or GitHub Copilot, API keys billed by usage, and the paid tools wrapped around them. Most developers have never seen that total on one screen. The gap is real enough that three spend-tracking tools launched on Hacker News in three days, between August 3 and 5, 2026.

Why is it so hard to know your total AI coding spend?

Because the costs of AI coding tools are fragmented by design. Subscriptions bill a card once a month, each on its own: Claude Pro at US$20, ChatGPT Plus at US$20, GitHub Copilot Pro at US$10, Cursor Pro at US$20, according to each vendor's official pricing page, checked on August 10, 2026. API keys from Anthropic, OpenAI or Google bill after the usage happens, so that number only exists when the invoice closes. Every vendor gives you a dashboard of its own consumption, and none of them shows the neighbors. The result is a total that nobody reads anywhere: it has to be assembled from card statements. A thread on r/claude on August 5, 2026 asked exactly whether other people had lost track of what they actually pay for AI coding tools, and the answers were the same story with different numbers.

How much does a typical AI coding stack cost per month?

A common individual stack in 2026 mixes one chat subscription, one AI editor and one agent CLI. Claude Pro (US$20) plus Cursor Pro (US$20) plus GitHub Copilot Pro (US$10) is US$50 per month before any API key. Add a usage-billed key for long agent sessions and the total stops being fixed: the same stack can close the month at US$60 or at US$150 depending on how much the agents ran. The problem is not that US$50 or US$150 is expensive for a professional tool; it is that the person paying usually discovers the number at the end of the month, not while it is being spent.

What tools exist to track AI coding agent spend?

Between August 3 and 5, 2026, three tracking tools appeared on Show HN, one per day. TokenMaxxer (August 3) tracks every AI token spent across coding tools. Aimeterly (August 4) builds per-user cost dashboards on top of Claude Code's built-in OpenTelemetry. CostClaw (August 5) is a local CLI that looks for spend leaks in Claude Code sessions. Each description comes from that tool's own launch post, linked above and re-checked on August 12, 2026.

Here is the part an earlier version of this article skipped, and it changes what the pattern is worth. Those three launches scored 7, 1 and 2 points on Hacker News respectively, with almost no comments. That is three builders reaching for the same problem in the same week, which is a signal about what builders notice. It is not a market voting for the category, and reading it as one would be reading our own convenience into a very small number.

Should you ration tokens or track them?

Rationing is what people do without visibility: switching to a cheaper model in the middle of a task, trimming the context the agent needs, stopping a run early because it must have cost a lot already. Rationing saves cents and silently costs quality, because the decision is made by anxiety instead of data. Tracking inverts this: when you can see which account, which project and which agent is consuming the budget, cost becomes a deliberate choice. Sometimes the right decision after tracking is to spend more on the agent that is delivering, not less everywhere.

Does the choice between subscription and API key change tracking?

Yes, because they fail in opposite directions. A subscription such as Claude Pro has a fixed price and a usage limit, so the risk is not a surprise bill: it is hitting the ceiling in the middle of the afternoon. An API key never blocks you, and that is exactly why it produces surprise invoices. Tracking a subscription means watching the limit; tracking an API key means watching the meter. We compared the two billing models, and where each one stops making sense, in Subscription or API key: what it costs to run multiple AI agents.

Can you see what your agents consume without another dashboard?

Partially, and it is worth being precise about the limits. CanvasCode, the Mac app that runs coding agents side by side on one canvas, shows one usage ring per active account in the footer and splits the usage panel by account (since version 1.12, June 2026). When agents work on a personal and a work account at the same time, you see each account's consumption of its plan limit, in one place, while it happens. That solves the surprise, not the accounting: CanvasCode does not consolidate invoices in dollars across vendors. For the billing truth you still need the vendors' dashboards or a dedicated tracker; what you gain on the canvas is knowing which account is burning its limit before the ceiling interrupts your afternoon.

Prices and product facts in this article were checked on August 10, 2026. The three Show HN links and their scores were re-checked on August 12, 2026.