Cursor, an AI-driven code editor designed to enhance coding efficiency, has experienced a notable increase in user-reported issues, particularly concerning application stability and support responsiveness. The project, managed by getcursor, emphasizes community feedback for iterative development.
Recent activities reveal a significant backlog with 964 open issues, highlighting user dissatisfaction with the Composer feature and API integrations. Critical bugs such as repeated crashes (#1840) and unresolved support queries (#1841) suggest a disconnect between user expectations and project support capabilities. Feature requests like localized deployment solutions (#1838) indicate demand for enhanced functionality.
Recent issues and pull requests (PRs) reflect a mix of critical bugs and feature requests that could impact user experience if not addressed. The development team comprises Arvid Lunnemark, Michael Truell, Aman Sanger, Edwiin Tsang, Dane Roelofs, and others. Their recent activities include:
Summary
Quantified Reports
Detailed ReportsSECURITY.md outlining vulnerability disclosure policy.The team's collaborative efforts focus on UI improvements and addressing community-reported issues.
| Timespan | Opened | Closed | Comments | Labeled | Milestones |
|---|---|---|---|---|---|
| 7 Days | 64 | 13 | 39 | 64 | 1 |
| 30 Days | 226 | 32 | 229 | 226 | 1 |
| 90 Days | 254 | 61 | 293 | 254 | 1 |
| All Time | 1763 | 799 | - | - | - |
Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.
| Developer | Avatar | Branches | PRs | Commits | Files | Changes |
|---|---|---|---|---|---|---|
| Arvid Lunnemark |  |
1 | 0/0/0 | 1 | 1 | 14 |
| Salifyanji J Namwila (Sheinstein) | 0 | 1/0/0 | 0 | 0 | 0 |
PRs: created by that dev and opened/merged/closed-unmerged during the period
The Cursor project has seen a significant uptick in GitHub issue activity, with 964 open issues currently logged. Recent submissions highlight user frustrations regarding various functionalities, particularly around the Composer feature and API integrations. Notably, there are recurring themes of dissatisfaction with the responsiveness of support, as many users express concerns over unanswered queries and unresolved bugs, indicating a potential backlog in issue resolution.
Several issues stand out due to their urgent nature, such as #1840, where a user reports repeated crashes of the application, and #1841, which calls attention to the lack of responses to numerous outstanding issues. This suggests a possible disconnect between user expectations and the project's support capabilities. Additionally, the presence of multiple requests for improved functionality—like localized deployment solutions (#1838) and enhanced AI model integrations (#1811)—indicates that users are seeking more robust features to enhance their development experience.
Most Recently Created Issues:
Issue #1848: Composer as a docked window instead of floating
Issue #1846: The @web doesn’t look for YouTube videos or Reddit posts
Issue #1845: Active Bar
Issue #1843: Bad CPU type in executable -- vscode plugin: Todo-Tree
Issue #1842: Stuck Gathering chunks using conversation history... for at least 20 minutes.
Issue #1841: Why are you guys not replying to SO MANY ISSUES? please ask someone to look into it
Issue #1840: Cursor is crashing again and again please fix ASAP URGENT
Issue #1839: Editor keeps adding "import { addIcons } from "ionicons"" to my angular class
Issue #1838: About localized deployment solution
Issue #1836: TS Server Keeps Crashing
These issues reflect a mix of feature requests and critical bugs that could impact user experience significantly if not addressed promptly.
This analysis highlights both the challenges facing the Cursor project in terms of user satisfaction and the potential areas for improvement that could enhance its functionality and user engagement moving forward.
The repository for Cursor, an AI-driven code editor, currently has two open pull requests (PRs) and a total of 79 closed PRs. The activity around the open PRs indicates ongoing efforts to improve issue templates and community engagement, though there are notable discrepancies in how contributions are being managed.
PR #1821: Cursor on the Web
PR #1539: chore/github: revamp issue templates
PR #501: remove invalid returns
PR #475: Update ci.yaml
PR #435 & PR #434: Fix conflict with Chinese input method
PR #417 & PR #416: Show history list under command bar
The current state of pull requests in the Cursor repository reveals several themes and patterns that could be critical for understanding the project's development trajectory.
Firstly, the two open pull requests (#1821 and #1539) highlight a focus on improving user interaction with the repository through better issue templates. However, the feedback provided on PR #1821 raises concerns about contributor awareness regarding submission guidelines. The comment from Tejas indicates that contributors may not fully understand how to use templates effectively, which could hinder community engagement and lead to frustration among users who wish to contribute. Such misunderstandings can be detrimental to project momentum and may require additional documentation or clearer guidelines.
Moreover, the age of some closed pull requests—such as PR #501 and PR #475—suggests potential bottlenecks in the review process or a lack of prioritization for certain types of contributions. The fact that these PRs remained open for over a year before being closed could indicate either a lack of resources dedicated to reviewing contributions or an overwhelming number of issues that need addressing. This could lead to contributor disengagement if they feel their efforts are not being acknowledged or acted upon in a timely manner.
Additionally, there is a noticeable trend toward addressing usability issues, particularly concerning internationalization (as seen in PRs #435 and #434) and user interface enhancements (#417 and #416). This responsiveness is commendable as it shows that the maintainers are attentive to user feedback and are actively working to improve the software's accessibility and functionality.
However, the overall volume of open issues and pull requests (966) relative to total commits (204) raises questions about project management efficiency. The high number of unresolved issues may overwhelm contributors and detract from their motivation to engage with the project further.
In conclusion, while there are positive strides being made in terms of user engagement and responsiveness to feedback, there are also significant areas for improvement in contributor management and project organization. Addressing these challenges will be crucial for maintaining momentum within the Cursor community and ensuring that it continues to thrive as an innovative solution in AI-driven code editing.
Arvid Lunnemark (arvid220u)
SECURITY.md file outlining a vulnerability disclosure policy, contributing 14 lines of code.Michael Truell (truell20)
Aman Sanger (Sanger2000)
Edwiin Tsang (boxizen)
Dane Roelofs (Rethora)
Others (e.g., Eric Zhang, Bekir Yörük, etc.)
SECURITY.md file.The development team is actively engaged in enhancing the Cursor project through regular updates, collaborative efforts, and responsiveness to community feedback. Their focus on security and user experience suggests a mature approach to software development within an open-source context.