What Happened
Cursor removed the cost column from its usage dashboard and CSV export. The new view shows only token counts, timestamps, and request IDs. The CSV now contains the same fields, but no monetary value.
The team said the change simplifies the UI and cuts data redundancy. Developers who use Cursor for billing transparency in production AI‑agent workflows will lose an easy way to audit spend directly from the platform.
Why This Matters for Builders
No Built‑in Cost Visibility
Teams can’t see how much a workflow or node is costing. They must pull token counts and calculate costs outside the platform, adding overhead.Budgeting and Alerts
Automation pipelines that alert on monetary thresholds lose that trigger. Builders must convert token limits to dollar values themselves and update alert logic.Data Export Consistency
CSV exports feed reporting and compliance. Without cost data, reports must be regenerated or enriched with cost calculations, which can break existing integrations.Opportunity for Custom Cost Tracking
The change pushes teams to add third‑party cost‑tracking tools or custom post‑processing steps. This restores visibility and adds flexibility.
FAQ
Q: Can I still see cost data in the Cursor dashboard?
A: No. The dashboard now shows only token counts and request metadata.
Q: How can I recover cost data for my workflows?
A: Export the token usage CSV and use Cursor’s pricing API or your own cost‑model formula to calculate dollar amounts. Alternatively, integrate a cost‑tracking service that ingests token counts.
Q: Will this affect billing or payments?
A: No. Cursor will still charge you based on token usage. The change only affects how you view that data.
Originally published on Automations Cookbook.
