This happened after updating to 1.7. Now its occuring after updating to 2.0. Models don’t show up except for GPT-5 and I can’t press submit on the agent chat. i disabled beta features and restarted multiple times.
Steps to Reproduce
type something in the chat and press submit.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
@deanrie - can we get some updates to your status page on the service (its completely out this morning with all model reporting backend calling issues (try again later)…
There are more than 100 new bugs in the last 48 hours, the Character Set issue makes your application do 2x or 3x the work as it required to before since it has to “reprompt” again and again.
The support is “pretty nonexistant” and even yesterday was reported as a “partial outage” - if your model backends arent working, then your service is “out”, plan and simple.
Can we see some quality controls (testing reports, stable/dev/preview channels) or some of the other trappings of a vetted SDLC process start to emerge somewhere,
im getting really tied of paying Cursor to be your day-0 beta tester!
@Daniel_Smith - Re: status page feedback - forwarding that internally. For critical blockers, the team typically prioritizes fixes based on forum reports like this one.
thanks @deanrie - however we see that in fact, your application reports “transient model connectivity issue’ - but in fact its cause your latest update cannot read the contextts we used right before the update and this is the error you are reporting.
Thanks for having a ambiguous error message that send us in a Network/Service issue, but in fact is hiding the fact that from one update to the next, we cannot rely on anything that we had before “working” (see the other chat) ..
Wonderful - spent time debugging cursor to get back where I was yesterday and following what is shown in your errors, but in the end, cant rely on those either.
Also had this issue with a previous version and had to turn of plan mode, uninstall everything and reinstall. Now with version 2.0+ plan mode toggle is gone, but this issue returned. Had to use a script from another thread to rename a custom plan mode I had that was causing the conflict. Works now, but man these bugs are huge headaches and wastes of productive time.