You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Title: Feature Request: Custom Analytics API for User Actions
Description
I'm trying to implement custom analytics for specific user actions in Cursor (like tracking when users click Accept/Reject buttons), but I couldn't find any official API to achieve this.
Current Situation
I've checked the GitHub repository and found some analytics-related code
When running the project locally (npm start), the UI differs from the latest release version
There's no clear documentation or API for implementing custom analytics
Feature Request
Would it be possible to:
Provide a public API for custom analytics tracking?
Allow developers to hook into specific user actions (like Accept/Reject buttons)?
Add documentation for implementing custom analytics tracking?
Use Case
This would be valuable for:
Tracking team-specific usage patterns
Gathering metrics on feature adoption
Understanding user behavior for custom implementations
Question
What would be the recommended approach to implement custom analytics tracking in Cursor? Is this something that could be supported in future releases?
I've checked the GitHub repository and found some analytics-related code:
The text was updated successfully, but these errors were encountered:
Title: Feature Request: Custom Analytics API for User Actions
Description
I'm trying to implement custom analytics for specific user actions in Cursor (like tracking when users click Accept/Reject buttons), but I couldn't find any official API to achieve this.
Current Situation
npm start
), the UI differs from the latest release versionFeature Request
Would it be possible to:
Use Case
This would be valuable for:
Question
What would be the recommended approach to implement custom analytics tracking in Cursor? Is this something that could be supported in future releases?
I've checked the GitHub repository and found some analytics-related code:
The text was updated successfully, but these errors were encountered: