What’s that? You FINALLY solved a spottily documented API issue and you’re ready to test?
Fantastic! Please start over again with no context.
Cursor… you’ve gotta remedy this no-way-out-no-win setup. Just let me dump the first half of the agent’s buffer or something.
Would you mind sharing the request id for this? It would be helpful if you could temporarily turn off privacy mode before re-making the request.
Then do cmd+shift+p > report ai action > select the composer request > copy
Then paste it here.
Pls did you solve it
Yeah I hit this, would have been nice to have a warning before this came up - or even knowing that this would happen seems it never did previously.
Couldn’t even get it to summarize what we had done which makes the new agent/composer dumb and looking in all the wrong places.
Saw there was another update, hoped that fixed it but no good 
Hey,
We’ve found the cause for this one, and should be rolling our fix in our latest update in the next day or two.
For context, we usually roll out auto-updates over the space of a few days to help us catch any bugs before we send it out to everyone, so an auto-update could be a few extra days, but you will be able to download the latest version manually from here:
i’ve downloaded and installed this version and am still having the same Conversation Too Long issues
Sorry if I wasn’t clear, the update isn’t yet available as we’re still testing the fix, but should be available by Monday!
The auto-updates aren’t instant, but the download link above always gives you the latest version, regardless of our auto-update procedure. So when the update is available with this fix, you can use that link to get it immediately.
this has been happening to me all day and is bloody infuriating. have had to restart a session 4 times today, and it has occurred mid breaking changes being applied so that each subsequent session is an exercise in having to reacquaint the AI with the project and merely trying to get back to where i was before it happened…and, each time i get almost back to where it was when everything was working properly, i get the Conversation too long message again and have to start the whole process over again. have wasted a full day like this. not sustainable…
i’ve downloaded and installed the new version. worked for 1 message and stuck again and can’t do anything getting the same error no matter what I do.
Conversation Too Long
Your conversation is too long. Please try creating a new conversation or shortening your messages.
This is differnt.
You need to start a new Compose Session…
Im getting same thing
Hey, this is something we are working on a fix for, and should be available soon!
With it, you should see this error a lot less, as we do some magic behind the scenes to try and keep your old chat history as context for the LLM in your next queries!
i just got this as i was having files updated 3rd time in same project when i move on to a new friend they end up messing up the site and i swear more than i need to.
paying for subscription to be angrier than normal isnt healthy.
Sorry I didn’t reply to this sooner. Holidays…
Does this fix also fix the Connection failed? Which doesn’t really say as to why? Just keeps giving same error even when trying/trying a different model. Assume its same/similar reason as long context.
Request ID:c0eeaf2f-80d4-429f-ac52-4925ed01722f
Frequency seems to be increasing… getting this a LOT…
