Tool call timed out after 5s (codebase search)

Bug Reports
1

Never was getting this error before, but on every model including auto it seems like cursor’s own codebase_search tool, it times out in 5s. I’ve seen people mentioning a 25000ms timeout but this is kind of wild, 5 seconds is never enough time to actually search our codebase, and never had an issue before. Is this new tool throttling? 25 → 5s is a huge loss for our org.

2

Hey, which version of Cursor are you using? Also, let me know which model you’re using. Does this also happen in the new chat?

3

So before I saw your response, I was on EA but switched to standard release. Not sure what I was on before but I’m on 0.49.6 now. And I followed someone else’s instructions/solution here: ⚠️Tool call timed out after 25000ms - #3 by scrollinondubs
Doesn’t seem to be timing out for me anymore. Hope this helps someone else!

4

Hello,
this is occurring again.
For a while after I followed the other instructions, I was getting quick tool calls – but honestly, 5s is too short regardless of if I’m falling under that threshold or not. Again, this never happened before.

Version: 0.49.6
VSCode Version: 1.96.2
Commit: 0781e811de386a0c5bcb07ceb259df8ff8246a50
Date: 2025-04-25T05:07:16.071Z
Electron: 34.3.4
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.4.0
Example Notes
Screenshot 2025-05-05 at 02.51.07
Screenshot 2025-05-05 at 02.51.07714×1830 150 KB
 In this screenshot, I had sonnet 3.7 manually selected (with thinking turned on). I find this happens with gemini as well as auto; as long as it’s trying to use the codebase_search tool.
1 Like
5

Tool call timed out after 5s (file search) - This has been happening for ages. An annoying bug.

6

Any feedback from the cursor team on this? @deanrie ?

7

Hey, try updating to version 0.50 and check if the same thing happens there. Let me know if the issue isn’t resolved.

9

Hello,
I’ve updated to 0.50.4 and am still getting Tool call timeout after 5s (codebase search).

To update, I fully wiped my installation as recommended in the possible solution.

  1. I deleted Cursor
  2. I deleted ~/Library/Application\ Support/Cursor/*
  3. I deleted ~/Library/Preferences/com.cursor.app.plist

Screenshot 2025-05-16 at 10.35.30
Screenshot 2025-05-16 at 10.35.301920×1200 79.3 KB

You can see Tool call timeout after 5s (codebase search). in the chat on the right side - this is using Auto model.

For me, the bug is still present. Either bring the tool call timeout back up to 25s at least for the internal codebase_search tool, or another short-term solution would be giving users control over their tool timeouts in general.

While I understand this constraint for custom MCP servers and tools, it’s really frustrating when it is Cursor’s own indexed RAG search tool that is timing out – it degrades trust that Cursor is actually capable of reading a codebase, which is the functionality we are most invested in the product for.

1 Like