Top Feautures for Cursor to become awesome again

Discussion
1

  1. Context is king - I hate false deletions, weird unrequested code changes and when Claude doest not find a function or module - the more serious coding gets, the more important it is to have smart codebase oversight and a sort of second view on deletions which might not be related to the initial request

  2. User rollback set points with database schema and db - sometimes I code into a direction to realize I went too far. Cursor’s rollback is ok, but if the db gets modified its an issue to go back and sometimes one can get lost in the rollback states. One should have an easy rollback manager which sits on top of the standard rollback which allows also to reinstate database states in full - also highlight it in the agent window visually where the user rollback point is

  3. A solution to the slow pool issue - happy to pay 50 to not get overy interrupted in my workflow. Currently this is a deal killer

  4. Better MCP integration - make it visual and easy and link into directories for easy integration

  5. Native browser tools for Chome which can directly access the whole source code and log

  6. Deep Figma integration with node level code grab so one can get 1:1 copies

  7. Architect mode and easier use of rules with own interface - planner and supervisor agent plus main coding agent

  8. Mixed model approach - have local and remote premium LLMs work together (via Ollama)

  9. No more crashes

Just some thoughts. But context and slow pool bug me the most. Architect would be great.

And yes, make an own linter model that runs locally.

2

This is called git. It already exists.

Architect mode and easier use of rules with own interface - planner and supervisor agent plus main coding agent

You can already make custom modes. Click the pencil icon next to the agent selection.

A solution to the slow pool issue - happy to pay 50 to not get overy interrupted in my workflow. Currently this is a deal killer

You can already pay for more fast queue requests???

the other ones would be nice tho.

1 Like
3

I know there’s git - but it still is not as effortless as it could be. Imagine seeing haing a rollback favorite button after each agent run which allows you to easily find the point among multiple in-between points.

I mean unlimited usage in say a medium pool for 50. I want unlimited … usage based bankrupts you

1 Like
4

I feel we all just need WORKFLOW teaching.

I post a bunch about barking orders at the bots, but there is so much nuance to properly prompting… BUT/AND there is a skill to knowing how to GUIDE the bots as you prompt.

Truly I think such is the mortar of how you bui;d with bots.

You should read my post about voice prompting as an example.