Feature request for product/service
Cursor IDE
Describe the request
- Chat‑Level Cursor Insights (Instead of Daily Aggregation)
Cursor Insights should be extended to provide analytics at the individual chat window level, rather than only aggregating conversations by day.
The goal is to allow teams to open a chat tied to a unique identifier (such as a JIRA ticket) and view insights specific to the full lifecycle of that conversation. This would enable teams to understand:
A. How many cycles were needed from start to completion
B. How effectively Cursor AI used the provided ticket and instructions
C. How the quality of tickets or repository instructions influenced the outcome
These insights can directly drive improvements to both process (ticket grooming) and product usage (Agent Instructions), ultimately changing how teams collaborate with AI to maximize efficiency.
- Exportable API for Insights, Usage, and Analytics
Developers should have access to an API that exports Cursor Insights, usage data, and analytics in CSV format, ideally scoped per chat window.
This would allow engineering teams to:
A. Pull structured data programmatically
B. Perform deeper analysis
C. Identify patterns, bottlenecks, and opportunities for improvement
Such an API would make it far easier for organizations to course‑correct, measure impact, and continuously improve how they work with Cursor.
Operating System (if it applies)
Windows 10/11