Agent is stuck on "searching files */**.<ext> in <dir name>..."

Describe the Bug

When I run a prompt the search stucks on “searching files */**. in …” where the ext can be anything from ts, py to multiple extensions also and dir name is the directory in which it’s searching file

Steps to Reproduce

I don’t know how to reproduce it some times happen sometimes don’t but from few days it’s happening too often

Expected Behavior

it should search file fast and move ahead but it stuck in searching and never comes out I have tried leaving it for 15-20 mins also

Operating System

MacOS

Version Information

Version: 3.10.20
VS Code Extension API: 1.125.0
Commit: 23b9fb205fe595ea2be29da7214e19762d037fc0
Date: 2026-07-07T07:03:33.071Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 24.5.0

For AI issues: which model did you use?

auto

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the report. This is a known issue: the agent can get stuck after the Grep or Glob tools on the searching files … step and then it won’t move forward, with no error and no timeout. We’re tracking it, but there’s no ETA for a fix yet.

To link your case to the tracker, please send the Request ID from the stuck run: open the chat, top-right chat menu > Copy Request ID. If Privacy Mode is enabled, the ID may not be available.

Temporary workarounds:

  • Stop the request and run it again.
  • If that doesn’t help, reload the window via Cmd+Shift+P > Reload Window.

A couple questions that can help narrow this down:

  • Do you have a .cursorignore, very large directories, or symlinks in the project?
  • Are you opening a specific workspace folder, or a high-level parent folder? On macOS, opening a narrow, specific folder instead of a huge parent folder noticeably reduces the chance of hitting this hang.

Send the Request ID and the details above and we’ll dig in. If there’s an update on the fix, I’ll reply in the thread.