When searching files through Cursor, it usually hits a timeout. Yet, I have no trouble locating files manually—even though it takes longer than 25 seconds. Is there a setting to extend the tool call timer?
@deanrie any idea on this?
increasing the limit makes no sense, as 25 seconds is already too long. Some tools have a higher timeout and then you just wait for tens of minutes until it fails.
I have a very large codebase, 100k+ files. So if Cursor try to search for example a method/function, it will take a long time. It often take more than 25 seconds when I am searching functions/methods myself. And I am not suggesting to change the timer for everybody. Just an option to control the timer in the settings.
1 Like
I would try to find ways to not have that many files 
and i know it sounds funny.
- Do you really need all 100k+ files at same time?
- Are they well organized? (some OS doesnt handle many files per folder well)
- Cant you just open Cursor on a subfolder (assuming you have something like modules or front/backend etc separated in the project)?
If your OS is not handling that many files so well, perhaps it would be good to see how to handle it, because there is very likely a certain limit from the AI side how long Cursor may be able to stick to a request hanging (while the tool is running).
1 Like