Yeah, I’m having the same problem, and there’s a spike forming on DownDetector, so I think this is another temporary issue on Cursor’s side. It’s happening with all the models I’ve tried.
This has been happening to me for about 3 weeks. I tried disabling HTTP/2 as some have suggested but that didn’t do anything. Closing cursor entirely and reopening it fixes it for a little while (maybe half an hour) but it always messes up again.
OK, that’s weird. Mine resolved itself within an hour or two, after whatever outage happened yesterday. (Here’s a screenshot of the spike on downdetector.)
I’m having the same problem repeatedly today. I’m using premium models and they are making a lot of tool calls but I get the error before the response is complete and code changes are suggested. Are we being charged for these errors? [Edit: Just checked an there is no charge for the errors]