Cody AI auto-applies diff-style changes without user approval after any query

Cody VS Code
, , ,
1

In the last few days, Cody chat in VScode has responded to any request with ‘Here is the proposed change:’ followed by diff-style output and tries to auto-apply it’s changes without any input from me.
This makes Cody chat completely unusable. If I were asking for code changes, the fact that Cody is applying text in a diff format which completely wrecks any code I have anyway, however, I’m not even asking for code changes. I was asking Cody to help me check my code for potential causes for a bug I’m struggling to diagnose properly.
Is there something going wrong on my end that I should look into?

3 Likes
2

Hey @the_nexust

This sounds like Sonnet 3.7. This model does overly more than asked and you need to put it on a leash. That means, your prompt needs to be adapted to this model.

3

I did think it might be a model specific issue, so I tried a range of models before reaching out.
I get the same result regardless of whether I’m using Claude, GPT, or Gemini. I watched the output just to be sure the chosen model was actually being used. I’m really not sure what’s going wrong.

4

Hi @PriNova Same issue, I’m also facing

5

I have exactly the same issue. No matter the model or the repository, I’m stuck on it.

6

So, I found a workaround. I downgraded it to a random past version (v1.72.0), and it works. It’s probably some update that got released with a bug.

7

Do you really mean 1.72 or 1.82? Because the step to 1.72 is very large for bisecting what the issue might be.

8

1.72. I went back to a random version from about a month ago. I haven’t messed with any of the others, though.

9

1.74.0 is the latest stable version that doesn’t have this new bug.

10

Hey @AlfredoSandoval

that is great information. That helps a lot for bisecting the commit range.

11

Fixed on latest pre-release (1.87.1744887451).

Thank you sir!

12

Great to hear. Thank you for your feedback

13

Hey @AlfredoSandoval some other users are reporting that for them the issue wasn’t resolved by upgrading. What did you do others don’t have been done? haha

14

Hey @PriNova - my bad just got to this. Looks like it’s still fine on latest pre-release 1.89.17 - but others should double check it

(working on VS Code (1.99.3) + Cursor (1.96.2)

1 Like