How all my bug reports to the Cursor team end up
I want to like Cursor. I really do. But there are some serious frustrations I have with the product and the project itself.
It's not just the pricing
This is the biggest gripe people have about Cursor, and it's understandable. They have been very unsteady with their pricing model, including a recent change raising the price of Claude 4 Sonnet from 0.75x requests to 2x requests per call. The devs recommend, if you are concerned about usage limits, to just use Auto model selection. But this comes with a significant reduction in quality because Auto will typically choose the cheapest model, and even goes against the recommendation of their own docs, which is "You should choose the model that works best for you".
Claude 4 Sonnet works best for me, so please let me use it.
The features that are missing
The biggest one is the ability to sync my settings across machines. This is a widely requested feature on their forums, yet the devs have stated it is not a priority. It is a feature that competitors like Continue have prioritized.
The features that are broken
Docs indexing. It is a major advantage of a tool like Cursor over something like Claude Code. Being able to send up-to-date documentation to the LLM.
Except it doesn't work consistently. The developers' response seems to be to manually fix URLs one at a time (or at least, one out of the dozens that are reported on this thread). But it's an issue that affects a significant number of sites, and the devs have not commented on or addressed the issue in any way.
Pretending an issue is not widespread when you see dozens of users reporting it is not the way.
The features that are present
POV when I open Cursor
They are pushing background agents hard. They've updated their web dashboard so the first page you see is a big "Agents" page. There are pushes toward background agents all over the place inside of Cursor itself. And I get why. Background agents increase your usage, which increases the amount they can bill you.
I have a lot of feelings on background agents. From not trusting an LLM to write correct code without supervision, to what they can do with unfettered access to my data, I don't generally want to use them.
And I want the option to disable them.
Cursor has a setting to completely disable them. But it doesn't work. About par for the course, I suppose.
The project itself
"Have you tried any of the extensions that offer this functionality?" When the developers offer a response to a feature request, it's dismissive like this. To be clear: any settings sync extensions for VS Code are no longer maintained because VS Code has settings sync natively. Cursor does not support VS Code's native settings sync. This also does not cover the issue of syncing Cursor's settings. The devs cannot think of any use cases like syncing user rules, MCP servers, or indexed doc sites.
And that is if you even get a response. Most likely, your bug reports will go ignored and unresolved, until they are automatically closed.
If this was an isolated example, that would be fine, but this is an issue that's been touched on in every section of this post.
And so, I will paru -Rns cursor-bin
Top comments (0)