Grepping- tool hanging issue?

Support Bug Reports
1

I keep having issues where i have to reload the whole vscode instance to be able to continue a thread. Stopping and writing continue doesn’t work.

Also when it dose reload a couple like a couple of the most recent ai tasks in the command line (like what it was stuck on) is gone.

Mostly using composer 2 but gpt 5.5 does it too.

Where does the bug appear (feature/product)?

Version: 3.2.16
VSCode Version: 1.105.1
Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0
Date: 2026-04-28T21:07:47.682Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Linux x64 6.17.0-22-generic
I

3

On top of that when i reload my chat history is reordered.

5

I’m experiencing the grep tool hanging issue as well. Subagents are hanging too.

Version: 3.2.16 (user setup)
VSCode Version: 1.105.1
Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0
Date: 2026-04-28T21:07:47.682Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Also, Agent sessions keep starting with “Warming up…” for some unknown reason.

6

Yeah 'im sure i had a sub-agent crash too.

7

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.

9

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?
  • @j-173 / @hadams42, are you also on 3.2.16? And what OS is @hadams42 using?

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.

10

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?

12

@Jason_Wu2 thanks for the detail about cloud-mounted storage and the workaround. That’s helpful context, high-latency filesystems can trigger the same class of ripgrep hangs.

A couple quick questions:

  1. Does the setting actually switch back, or does indexing just restart? Open settings.json Cmd+Shift+P > Preferences: Open User Settings (JSON) after you turn off Index Repositories for Instant Grep, restart Cursor in the morning, and check if the value is still false in the JSON. If it’s false but indexing still runs, that’s one bug. If it flipped back to true by itself, that’s a different bug. Let me know what you see.

  2. More targeted workaround. You can add the heavy cloud-mounted paths to .cursorignore in the workspace root. That will exclude them from indexing including Instant Grep without fully turning the feature off. Default ignore list is here: Ignore File | Cursor Docs

  3. Extra info for tracking. Which cloud storage is it exactly, S3FS, sshfs, NFS, SMB? Also what OS, and what Cursor version?

On the main grep hang, it’s the same issue we’re discussing above, no ETA on a fix yet.

13

I opened up cursor this morning and saw that the instant grep was automatically enabled again. This also happened again after I installed a new update to cursor this morning. I did this by opening up a new cursor window to get to the home page both times. In my settings.json file, I don’t see anything related to this instant grep
Below are the settings.json commands that are related to cursor itself:
“explorer.confirmDragAndDrop”: false,

“cursor.composer.textSizeScale”: 1.3,

“git.openRepositoryInParentFolders”: “never”,

“window.autoDetectColorScheme”: false

{

“window.commandCenter”: true,

“cursor.general.disableHttp2”: true,

“workbench.colorTheme”: “Visual Studio Dark”,

“terminal.integrated.enableMultiLinePasteWarning”: “never”,

“remote.autoForwardPortsSource”: “hybrid”,

“remote.SSH.defaultExtensions”: [

“ms-toolsai.jupyter”,

“ms-toolsai.jupyter-renderers”,

“ms-toolsai.jupyter-keymap”,

“amazonwebservices.aws-toolkit-vscode”

My clous storage is AWS s3, I am on Rocky Linux version 8.8. After the update I installed this morning, I am on cursor version 3.3.30

14

@Jason_Wu2 thanks for the details.

To separate the two issues:

  1. Toggle persistence. If there’s no Instant Grep key in settings.json after you turn it off, it might mean the off state isn’t written to JSON and is stored in app state. One quick test: turn the toggle off, quit Cursor completely via Cmd+Q or Ctrl+Q, then open it again without rebooting and without updating. Does it stay off? If yes, the reset is triggered by either an update or something at the OS session level. If no, the off state isn’t persisted between launches at all. This helps narrow down the cause.

  2. A more reliable workaround for your case. Instead of turning Instant Grep off every time, add the S3-mounted paths to .cursorignore at the workspace root. That will exclude them from indexing including Instant Grep, while keeping the feature working for local files. Docs and the default list are here: https://cursor.com/docs/reference/ignore-files

On the main grep hang, it’s a known issue and there’s still no ETA. As soon as there’s an update, I’ll post it here.