Thanks for reporting a bug you have found in Cursor!
Please add the following info to help us diagnose your issue:
Did not find it in forum.
Provide a clear description of the bug:
When a chat gets long, it suggest starting a new chat, and it starts a new chat with context from the previous chat loaded as an attachment(you can hover over it and it will give a summary). Recently, when you do that, it has started to act like it’s generating, then just stops like you never hit send. When you remove the attached previous chat summary/context, however, it will then work.
It used to work fine, but last week it started doing this. I’m on the latest macOS. I can still use Cursor by removing the attached context.
Here’s a screenshot of the initial button. Forgot to include it.
Hey, could you please provide the version of Cursor? Also, what error are you getting after sending your request with the attached chat context?
FWIW I ran into this today as well (when starting a new chat from a prior one, the new chat starts to generate then stops – restarting Cursor or trying another new chat, or a different LLM model – ie. Claude instead of Gemini – doesn’t fix it either). As you mentioned, the fix seems to be to remove the auto-summary/context attachment – then it will successfully start a new chat!
Interestingly, it looks like we might be using a similar semi-manual context workaround in the meantime, with a .md file generated by the LLM to pass to the next LLM for context on where to pick up.
I’m on Windows using 0.48.8 of Cursor. Not sure if it’s related, but I started the new chat after the last one was glitching and either hallucinating or surfacing underlying Cursor-side <user_query> messages in plain text during their turn from “me” and then getting cut off automatically. Typically whenever I run into that glitch I have to start a new chat in the codebase to fix it – IIRC this is the first time I’ve run into issues starting a new chat, though, after that.
Also, to deanrie’s question, there isn’t an error message (at least not one that surfaces anywhere clearly visible – it’s possible there are some Cursor logs somewhere I’m not aware of that are actually logging an error, but it’s not on the frontend UI – it just starts generating a chat then stops).
This is currently and still happening, nearly every single time I continue a chat using the New Chat button beside the text: Start a new chat for better results.
