Bug Report: Cursor Agent Repeatedly Hangs at “Explored 2 searches”
Description
When using Cursor in Agent mode, after submitting a prompt, the interface enters a prolonged waiting state with no response or output. The UI then freezes at the state shown in the attached screenshot: the Agent workflow hangs at the “Explored 2 searches” step, displaying “Thought for 1s”, “Searched files /lls/”, and “Grepped streamlit”, but never proceeds further. It neither returns a result nor throws an error. This issue has occurred repeatedly and is consistently reproducible.
Steps to Reproduce
Open Cursor 3.4.20, switch to Agent mode, and select Auto as the model.
Type a prompt in the input box and submit it.
Observe that the Agent initiates “Explored 2 searches”.
The UI sequentially displays “Thought for 1s”, “Thought briefly”, “Searched files /lls/”, and “Grepped streamlit”.
After these steps, the workflow completely halts. There is no further output, no error message, and the interface remains stuck indefinitely.
Expected Behavior
The Agent should complete the search and reasoning workflow and return a full response. If an execution failure occurs, it should provide a timeout notification or an error message.
Actual Behavior
The Agent repeatedly hangs after the search phase.
No error is thrown, the process does not continue, and no valid output is returned.
Every reproduction stops at the same “Explored 2 searches” step.
Attachments
Screenshot: The red-boxed area shows the Agent stuck at the “Explored 2 searches” state, with Thought / Searched files / Grepped steps completed and no subsequent progress.
Additional Context
This issue is consistently reproducible on the Stable / Early Access release track.
The Auto model is used without manually specifying a particular model.
The project path contains files related to lls, with the search scope set to **/lls/**.
Hey, this is a known issue: the agent can get stuck after using the Grep or Glob tools and won’t move forward. It’s been reported and is being tracked, but there’s no ETA for a fix yet.
A couple things that would help:
Share the Request ID from one of the stuck runs open the chat, then top right chat menu > Copy Request ID. If Privacy Mode is on, the ID may not be available.
As a temporary workaround, if it gets stuck, try stopping and restarting the request. Sometimes Reload Window via Cmd+Shift+P helps. If we have an update on the fix, we’ll reply in this thread.
Same issue with Sonnet 4.6:
108ab2e0-c326-47ad-b591-e376feec2906
7660c20a-06f0-4c90-b376-6dd29fb86afc
99e6a937-b508-4120-8355-5e3f00127773
de706de0-e00f-4036-8484-33c1e0557fa9
Hey @tcy, thanks. I grabbed the Request IDs and I’ll attach them to the ticket. Good to know this bug happens not only on Auto, but also on Sonnet 4.6 + the Default track, that helps narrow it down.
Same issue as above: the agent hangs after Grep or Glob. We’re tracking it, but there’s no ETA for a fix yet.
Workaround until it’s fixed:
Stop the request and restart it
If that doesn’t help, Reload Window via Cmd+Shift+P
If you have a .cursorignore, very large directories, or symlinks in the project, please mention that too, it helps narrow down the cause. Once there’s an update on the fix, I’ll reply in the thread.
