It worked properly yesterday. But today Claude in long context mode (haven’t tested in other scenarios) suggests a file name and then code changes, but there is no file name at the top of any code suggestion, so it’s then necessary to perform 3 clicks instead of one as before. Earlier we would just click ‘apply’ and it would instantly apply. But now it’s necessary to first click the file name in the chat, then hit apply and then hit confirm.
Update: seems to be working correctly again as of Aug 29th.
I’ve talked to Cursor team and they are aware of the bug with Apply not autodetecting the file. They said they are investigating this and will try to find a solution
How do you guys manage your backlog? I’ve seen multiple tickets marked as ‘solved’ yet these clearly aren’t.
Polite suggestion, it’d be helpful to provide an open issue link so we can track and follow along, else we think things are sorted, only to realise they are not, and open a duplicate ticket - which helps no one (including your team).
Seems like this is a different one. This one is about AI not predicting the file name correctly (which results in Apply being slow), and the one in the link (which I’ve seen reported a lot lately) is about Apply incorrectly prepending AI suggestions to existing code instead of modifying the existing code
This issue is still not solved I’m facing the same problem also The chat is not recognizing my code base. Didn’t have this issue until I upgraded to pro. Not sure why that made a difference but maybe it was a coincidence because those things are real.
Yeah, it was probably a coincidence. This works randomly for me, and occasionally it would autodetect the file correctly many times in a row, and occasionally it wouldn’t for some reason