Cursor · Mistakes

Context mistakes

Stop wrong-file edits and duplicated code, know when to start a new chat, and cut rules and MCP servers that crowd the context.

Cursor context mistakes

Too little and too much look similar

Both produce confident work that's off target. With too little context, the agent guesses at files and patterns. With too much, your instruction competes with long rules, stale conversation and irrelevant results. The context ring and a look at your last prompt will usually tell you which one you're dealing with.

Change the setup, not just the prompt

If you've made the same correction twice, a better prompt won't stop it happening a third time. Write the fix into a rule, exclude the competing files with .cursorignore, or start your work with a read-only step in Ask mode. Then the next chat starts in a better place.

Frequently asked
Why does Cursor keep editing the wrong file?

It's probably choosing between similar matches, such as two config files. @-mention the exact path, say which folders to leave alone, and exclude generated copies with .cursorignore.

Why does Cursor create a function that already exists?

Cursor's course calls this changing before understanding. Ask Agent first to show how the repo already handles the task and where shared code lives, then ask for the change using that code.

When should I start a new chat in Cursor?

When you switch tasks, finish a feature, or see the agent going in circles. Cursor's course says it's worth continuing while you're on the same feature and the earlier context is useful.

Can too many rules hurt Cursor?

Yes. Cursor's course says too many rules consume unnecessary context and may confuse the agent. Keep always-on rules short, scope others with globs, and move occasional procedures into skills.