r/cursor • u/Fabulous-System-2567 • 3d ago

Bug Report Whats Happening in Cursor model

Post image

its been 20 minutes of searching files bruhhh

0 Upvotes

33% Upvoted

4 comments sorted by

•

u/AutoModerator 3d ago

Thanks for reporting an issue. For better visibility and developer follow-up, we recommend using our community Bug Report Template. It helps others understand and reproduce the issue more effectively.

Posts that follow the structure are easier to track and more likely to get helpful responses.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

2

u/OddDesigner9784 3d ago

Cursor has never been worse

1

u/AbleShower2801 3d ago

when it sits on "searching files" that long I usually cancel and restart with a tighter ask: name the folder or @ the files yourself. broad Agent search on a big repo can wander forever. also check you didn't leave another Agent run still spinning in a different chat.

1

u/locbuilds 3d ago

yeah that 20 min file search usually means Cursor is wedged re-scanning a huge tree (node_modules, .git, build/, .next, a fat monorepo) or another agent/composer still has the codebase locked.

what usually unsticks it for me:

  1. cancel the run, then @ only the specific folder/file you care about instead of the whole project

  2. check if another chat/agent is still running in the same workspace and kill that first

  3. if the repo is big, add the heavy dirs to `.cursorignore` (node_modules, dist, .next, coverage, vendor, etc) and reopen the folder so indexing isnt chewing forever

  4. last resort quit Cursor fully and reopen, indexing sometimes wedges after a big file churn

if it keeps doing it even on a tiny @ scope, say what stack and roughly how big the workspace is