Feature request for product/service
Billing
Describe the request
There is no reliable way to map token usage to a specific project. We want to run analytics on model and token usage per project (cost attribution, trends, comparisons across repos).
In other agent harnesses, token usage is included in the JSONL session logs or in a SQLite db. Combined with repo/cwd information from those same logs, we can attribute usage to projects. In Cursor, that link is missing.
The dashboard CSV export also does not include a session identifier. Even that alone would be enough for us to join usage data with our own session/project metadata and build the mappings ourselves.
What would help:
- Native per-project usage stats with Model and usage details in Cursor (ideal, but we understand this may be hard to generalize across workflows).
- Session identifiers (and ideally project/repo/cwd context) in usage logs or CSV export, so we can join usage to projects on our side.
- add a session ID column to the dashboard CSV export.
Why this matters:
Without project-level attribution, teams cannot answer basic questions like “which repos drive most of our token spend?” or “how did usage change after we adopted Cursor on project X?”