Cursor is absolutely broken

[jrista]

Cursor has its issues. I’ve been programming for over 30 years, been in the industry around 27 or so, and Cursor needs STABILITY. However, the issues with cursor, are not really with the code it generates, but with the reliability and stability of the features it contains: connectivity issues, broken terminal connections, hangs, crashes, etc.

In your case, my question is this? HOW ARE YOUR RULES?! Rules, rule. I suspect you don’t have good enough rules to govern the agent+llm, or INFORM them of your preferences.

See my response to another thread here:

Procedural programming

Rules. They are fundamentally critical to getting Cursor Agent and an LLM to build good quality code. Further, rules shouldn’t just be a few lines, a little blurb here or there. Rules need to be comprehensive, nuanced, detailed. Because otherwise, you end up with LOOPHOLES all over the place. I started with simple rules, but very quickly my rules became like the below example, after a few cycles of having the Agent itself, check my rules for loopholes and close them. This rule has been iterat…

The agent, without proper guardrails, the llm, without proper instruction, will generally do whatever they want! YOU must be the one to control the situation. Rules, do that. Don’t skimp on your rules.