Persistent Tool Call Timeout Issues in Cursor AI

Support Bug Reports
1

Issue Description

Cursor AI is consistently timing out (after 200000ms) when attempting to perform code operations. Multiple attempts with different approaches all result in the same timeout error.

Steps to Reproduce

  1. Attempt to make code changes through Cursor AI
  2. Even when breaking down the changes into smaller chunks
  3. Multiple attempts with different approaches

Current Behavior

  • Each operation times out after 200000ms (200 seconds)
  • Multiple attempts with different approaches yield the same timeout result
  • Even breaking down the operations into smaller chunks does not resolve the issue
  • The timeout occurs consistently across different attempts

Impact

  • Unable to make necessary code updates
  • Blocking development workflow
  • Multiple retry attempts required

Environment

Version: 0.45.11
VSCode Version: 1.96.2
Commit: f5f18731406b73244e0558ee7716d77c8096d150
Date: 2025-02-07T09:43:58.555Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.3.0

Attempted Workarounds

  1. Breaking down operations into smaller chunks
  2. Using focused, smaller edits
  3. Multiple attempts with different approaches
  4. Targeting specific sections of code

None of these workarounds resolved the timeout issue.

Priority

High - This issue is blocking development progress and needs immediate attention.

Additional Notes

  • The timeout limit seems to be consistently set at 200000ms
  • The issue persists regardless of the size of the operation attempted
3 Likes
2

I had the same issue. It was a problem with my cursorrules that was causing it keep running such as a DO NOT STOP UNTIL instruction

1 Like
3

Correction. not fully resolved but definitely helped

1 Like
4

Good news - we’re actually working on adding longer timeouts for MCP tools soon which should help with this! Keep an eye on our changelog, as that is likely where it’d be mentioned once available.

4 Likes
5

This is still an issue. It’s quite frustrating!

1 Like
6

Brother, when will this feature be updated

7

Hey, are you still seeing issues with tool calls timing out?

If so, can you share a request ID with privacy mode disabled:

8

At present, the MCP service cannot maintain a connection for a long time. When I do not operate for a period of time, I need to re-establish the MCP connection. I need the MCP connection to remain normal for a long time.

乐聊图片1751354445060
乐聊图片17513544450601265×733 40.4 KB

9

Hello dan, please find the request ID. Facing this issue frequently -
246e3e2f-4ae3-4dd4-b238-88def50c7530
email - [email protected]

10

as of 12/10/2025 this still appears to be a persistent issue. It takes 12 seconds to start my app and the agents terminal times out even before then. Something is very much not right imo

cursor_verify_isaac_lab_teleop_newton_s.txt (37.9 KB)

11

This is still an issue! It’s really frustrating. This never happened when I use copilot :broken_heart:

12

i fix similar problem fromt set ‘trust mode’ for current folder directory