i have the issue that the composer agent says that openAi isnt reachable,
but im using sonnet 3.5 
sadly since some weeks i have several issues with the composer not running properly.
i get always the same issues with “internet connection lost” but my connection is absolutly perfect or that the composer stops working because of a response limit or agent limit.
i needed to buy several times more fast responses the second month in a row because the composer acts really weird after a while.
the problems persist if i open a new composer window or the composer acts like the chat then or says that my prompt is to long but i just entered 5 lines of instructions.
now i get the openAi bug over and over again.
its so frustrating that i constantly run trough fast promts with those errors that i can only fix if i go back a few prompts and revert everything the composer already did for me!
im using claude sonnet 3.5 and not any openAi model.
now after opening a new composer window and just 1 prompt:
next fast request burned for nothing, what the hell is going on today? its getting worse and worse almost daily
Hey, this happens when you send your requests to the model too frequently. It’s a limitation of OpenAI, not Cursor. When you encounter this, try taking 3-5 minute breaks, and it should solve the problem.
buddy im using claude sonnet 3.5 and not a model of open ai?!
whats going on latly, i have non stop issues like that over and over again since last month and it gets worse almost daily. i burned through 1500 request last month because the composer made a huge mess with my entire codebase and i needed all the request to clean everything up again.
this month i burn through a lot of request with asking the composer the exact same thing but it does something else or doesnt do its job completly and edits a file 20 times over and over again
it gets worse and worse
after using the terminal to look for errors it starts guessing again where the typescript errors are:
Ah, sorry, I didn’t notice the model you selected. This is even stranger than I thought. We’ll try to figure it out. Sorry for the inconvenience.
it tried to make a script work 72 times and still failed
i get non stop issues since at least 1 week and i need to find new ways to work around the flaws that it has but now im at a point where i have no idea how to work around this
now its just un usable even if i open a new composer window, my entire codebase is a mess now and the composer created various empty folders or creates files in a complete wrong directory etc.
just burned almost another 1500 request this month just to be at a worse state than before 
i want a refund! the last updates messed everything up
Hey,
Regarding your first issue about the connection errors, this was an issue with one of our upstream providers that should now be fixed!
I’m sorry the composer agent has not been performing great for you so far! It’s our newest feature so we’re still trying to tune it to be as helpful as we can!
If the composer has messed up your codebase, you should be able to revert it to the state it was in before the requests, using the checkpoints.
You can learn more on that here: Cursor - Build Software Faster
There are a few tips you may find of benefit, such as starting new composer sessions whenever you are working on a new feature, or a different part of your code. Also, telling the AI to “look at the file before you make any changes” is also useful if the agent if losing track of the state of your files!
I understand you have had a bad experience, regardless of my suggestions above, and we apologise for that.
If you would still like a refund, drop us an email at hi@cursor.com and we’ll be happy to get one sorted for you.
2 Likes
so many problems and it gets worse every week
really edit out the name of a competitor? are you guys that desperate?