Composer adds advice to remove linter errors in almost every response!

General
1

Two days ago, I prompted Composer to advise me on resolving some linter errors in a Next JS project.

No problem; the response was appropriate.

However, the following day (yesterday), quite a few responses to my prompts in the same project resulted in correct responses, but would also add generic advice about how to resolve linter errors, when I have not mentioned it, and there were no linter errors.

Today, approximately 75% of responses to any prompt, include generic advice about how to resolve linter errors. I have not mentioned linter errors in a prompt since two days ago, and there are no linter errors.

This is just irritating more than anything else, because it’s unnecessary noise in the response.

Today I added a rule in the cursor preferences:

“Do not mention linter errors unless explicitly mentioned in a prompt.”

…but this has not made any difference.

Is anyone else having a similar problem, or can anyone suggest a way to prevent this happening

2

Hi @digitalic

Are you using the same Composer where error notifications were mentioned before? If you’re getting responses you don’t need, just start a new Composer, and that should fix it.

1 Like
3

Thank you for this suggestion; I only just noticed your response.

I was using the same Composer; it hadn’t occurred to me to start a new one.

Thanks.

4

Did this fix your issue?

5

Prior to your suggestion, the issue had only occurred a couple of times over the course of several hours (whereas it had been occurring for almost every response prior to that).

I have only used Cursor for a few hours since you suggested using a new Composer, and I haven’t seen the issues occurring, so it’s looking positive.

If it happens again in the new Composer I will post here.

Thank again for your input to this issue; much appreciated.

1 Like