Cursor 1.0

Viewed 193
Cursor 1.0 has received mixed feedback from users, highlighting several challenges and missed opportunities. Users appreciate the potential of Cursor but are frustrated with its compatibility issues, particularly with VSCode. Comments reveal concerns about the lack of updates for extensions, inefficient memory usage due to multiple MCP server instances, and incomplete features related to multi-root repository support. The need for clear differentiation between model-generated code and user-generated code also emerged, along with criticism regarding the product's marketing strategies and overall communication. Key points include: - Problems with VSCode compatibility and extension availability. - Memory issues from running multiple MCP servers. - Requests for better support for multi-root repos. - Calls for clearer documentation on model changes in coding. - Concerns over Cursor's marketing compared to competitors, emphasizing the need for clearer product communication.
0 Answers