Too quick to add yet more debug messages

If there’s one major gripe I have when using cursor it’s the constant desire it has to just add more debug to the code.
I don’t know if this is just Claude but whenever I paste in an error or rpt file the first response is almost always

“Lets add some more debug code to see what’s going on”.

Yet 99% of the time if I respond with something like

“before you add debug messages I want you to step through the code and see if you can see what the issue is”

it inevitably just finds the error and fixes it.

In fact as I’m typing this I got the message

“I suspect fn_createTasks isn’t being called at all, would you like me to add debug messages so we can see what’s happening?”

To which I replied

“can’t you just look and see if fn_createTasks is being called?”

and would you look at that it found the issue straight away :man_facepalming:

I don’t need debug code for every little error I just want it to look through the code and work it out like I would only much faster :slight_smile:

I’ve even tried adding

“Before you add debug messages I want you to step through the code and see if you can see what the issue is”

to the rules but it doesn’t seem to help

Is this in the chat, or in the composer?

Sounds trite, but try this:

IMPORTANT: Do not add debug messages until you’ve stepped through the code to identify the issue.