AI Pulse · AI Trends Pulse

Cursor users woke up to find their billing dashboard no longer shows the cost breakdown per API request. The change also hit CSV exports. A Hacker News thread with more than two hundred comments lit up with complaints from teams trying to run chargebacks or track spending by project. Cursor has not issued a statement, so treat this as developing.

The frustration is straightforward. When you run AI tooling across multiple teams or clients, you need granular usage data to bill accurately or spot runaway costs. Removing per-request detail turns a ledger into a lump sum. One commenter said their finance team now cannot reconcile which department drove a spike in usage. Another noted they were evaluating Cursor partly because the transparency looked better than competitors. That edge just evaporated.

This is a reminder that vendor dashboards are not neutral infrastructure. They are policy decisions dressed as product features. When a company pulls visibility without warning, it signals either a shift in how they want customers to think about cost or a step toward bundling that hides unit economics. Neither is great if you are the one writing the check. The thread is full of speculation, some of it reasonable, some of it not, but the core complaint stands regardless of motive.

If you are running AI tools at any scale, you need your own usage tracking layer. Relying on a vendor’s dashboard leaves you exposed to changes like this. An AI command centre built in-house or with a partner gives you a consistent view of spend, usage, and performance across every tool in your stack, no matter what a vendor decides to show or hide. It is not paranoia. It is just good operations when the tools move faster than the contracts.