3 May and I am having the exact same symptoms, beginning a few days ago. I am a heavy Cursor user and this is making the tool very difficult to be productive with. It doesn’t seem to matter whether I am using Composer 2 or a Claude model.
Hey, thanks for the report. This is a known bug. The grep/search tool can sometimes hang in a tool call and the agent can’t get out of that state. The only way forward is to reload the window. This overlaps with something we’re already tracking, so I can’t share an ETA for a fix yet.
To help us match your sessions to logs, it’d be useful to grab the Request ID for one hang:
In the chat where it hung: top-right chat menu > Copy Request ID
Paste it here (from anyone who hits it next)
A couple quick questions:
Does the hang happen right when grep starts, or after a few successful tool calls in the session?
About side effects after reload (mixed chat history, last shell commands disappearing), that’s expected. Any in-progress terminal operations are lost on reload window, and chat order is restored from local state. If you can reproduce this reliably even without a hang, let me know and we’ll look at it separately.
I have been having the same issue, but whenever I see my cursor chat trying to do a grep, it freezes at that point and eventually crashes my AWS instance. I have fixed this issue by turning off “Index Repositories for Instant Grep”, but this option seems to be automatically turned on whenever I open up my computer at the beginning of the day. I believe this is because the Index New Folders/Index Repositories for Instant Grep is very slow on cloud-mounted storages which is what I use to store my files. Is there a better solution to this problem besides me turning off Index New Folders and Index Repositories for Instant Grep?