Persistent Tool Call Timeout Issues in Cursor AI

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
1 Like
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.

2 Likes