Cursor is awesome, and I love using it! However, I’m struggling a bit with keeping it under control, especially when working with large, unfamiliar codebases. My main challenge is getting it to slow down and discuss changes before making them.
Currently, I’m using these simple rules to achieve what I call an “anti-YOLO” approach:
When making changes to my code, please:
- Propose ONE change at a time with surgical precision
- Explain each proposed modification thoroughly before implementation
- Include the exact code changes you recommend in your proposal
- Wait for my explicit approval before implementing any change
- Never modify multiple code snippets simultaneously
This helps somewhat, but Cursor still sometimes generates and runs code without waiting for my approval (maybe I’m missing a setting?). What I really need is for it to never change code without me understanding and approving the change first.
Would anyone be interested in a “Surgeon Precision” mode that:
- Forces single-change at time
- Requires explicit approval for each step
- Provides detailed before/after comparisons
I know this might use more chat messages and cost more, but when working with critical or unfamiliar code, this careful approach feels essential.
Has anyone found better ways to achieve this kind of careful, step-by-step workflow in Cursor? Or are there already plans for something like this?
Would love to hear your thoughts!