Cursor removes the dollar-cost graph from its usage dashboard
The CSV break was accidental and is fixed; the graph is gone for good. How to still see your spend — and YC open-sources its qm multi-agent harness.
Copy markdown
The graph Cursor quietly pulled
Cursor removed the dollar-cost usage graph from its dashboard, along with a small cost indicator near the context meter. Staff say the graph mixed plan usage with on-demand costs and was confusing — but the practical result is no at-a-glance view of what your account is spending.
The CSV scare was a bug, now fixed
Cost columns also vanished from the usage CSV export on Aug 1, which is what set off the outcry. A Cursor engineer says that one was accidental — collateral from a feature-flag cleanup — and the export is already restored. So per-request cost still lives in the CSV; it's the dashboard graph that's gone for good.
How to still track your spend
The restored CSV export and the /teams/filtered-usage-events API still return per-request cost, so teams can pipe spend into their own tracker; the open-source Cursor Cost Explorer already does exactly that. Worth wiring up before renewal season if you lean on Auto or Router to pick models for you.
Why this stings for builders
With Router silently sending requests across models, the dollar graph was the fastest way to spot an expensive model left running. Lose it and cost surprises get easier — and teams lose the number many used to justify their Cursor seat count at renewal.
Elsewhere: YC open-sources 'qm'
Y Combinator open-sourced qm, an MIT-licensed multiplayer agent harness that runs in your own Fly or AWS account with native Slack and web UIs. Each teammate gets an isolated sandbox plus shared rooms, and it plugs into Claude Code, Codex, OpenCode, and Pi — a weekend project if you want company-wide agents without vendor lock-in.