Fix a Bug by Explaining It Out Loud to the Editor

Open the file and type the bug as a question, including what you expected and what happened. Cursor reads the repo context you don't restate.

Accept the smallest fix it offers first. A one-line change is easier to verify than a rewrite it's proud of.

If it suggests touching files far from the bug, stop. That's a sign it misunderstood the scope.

The lag on a big index is real. For a huge repo, narrow the chat to the folder, not the whole tree.