# Persistent Tool Call Timeout Issues in Cursor AI **URL:** \ **Category:** Bug Reports\ **Created:** [February 14, 2025, 3:05am UTC](https://forum.cursor.com/t/persistent-tool-call-timeout-issues-in-cursor-ai/50861 "2025-02-14T03:05:19Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![mohamedeltwony](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohamedeltwony/32/26292_2.png) [@mohamedeltwony](https://forum.cursor.com/u/mohamedeltwony)\ **Post date:** [February 14, 2025, 3:05am UTC](https://forum.cursor.com/t/persistent-tool-call-timeout-issues-in-cursor-ai/50861/1 "2025-02-14T03:05:19Z")
## 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 ---
**Author:** ![jontintl](https://avatars.discourse-cdn.com/v4/letter/j/df788c/32.png) [@jontintl](https://forum.cursor.com/u/jontintl)\ **Post date:** [February 16, 2025, 6:06pm UTC](https://forum.cursor.com/t/persistent-tool-call-timeout-issues-in-cursor-ai/50861/2 "2025-02-16T18:06:49Z")
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 ---
**Author:** ![jontintl](https://avatars.discourse-cdn.com/v4/letter/j/df788c/32.png) [@jontintl](https://forum.cursor.com/u/jontintl)\ **Post date:** [February 16, 2025, 7:53pm UTC](https://forum.cursor.com/t/persistent-tool-call-timeout-issues-in-cursor-ai/50861/3 "2025-02-16T19:53:47Z")
Correction. not fully resolved but definitely helped ---
**Author:** ![danperks](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/danperks/32/19087_2.png) [@danperks](https://forum.cursor.com/u/danperks)\ **Post date:** [February 26, 2025, 12:04am UTC](https://forum.cursor.com/t/persistent-tool-call-timeout-issues-in-cursor-ai/50861/4 "2025-02-26T00:04:29Z")
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. ---
**Author:** ![wjaleks](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/wjaleks/32/51469_2.png) [@wjaleks](https://forum.cursor.com/u/wjaleks)\ **Post date:** [May 2, 2025, 6:27pm UTC](https://forum.cursor.com/t/persistent-tool-call-timeout-issues-in-cursor-ai/50861/5 "2025-05-02T18:27:40Z")
This is still an issue. It’s quite frustrating! ---
**Author:** ![jiezhonghu](https://avatars.discourse-cdn.com/v4/letter/j/779978/32.png) [@jiezhonghu](https://forum.cursor.com/u/jiezhonghu)\ **Post date:** [June 13, 2025, 11:26am UTC](https://forum.cursor.com/t/persistent-tool-call-timeout-issues-in-cursor-ai/50861/6 "2025-06-13T11:26:27Z")
Brother, when will this feature be updated ---
**Author:** ![danperks](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/danperks/32/19087_2.png) [@danperks](https://forum.cursor.com/u/danperks)\ **Post date:** [June 17, 2025, 8:48pm UTC](https://forum.cursor.com/t/persistent-tool-call-timeout-issues-in-cursor-ai/50861/7 "2025-06-17T20:48:45Z")
Hey, are you still seeing issues with tool calls timing out? If so, can you share a request ID with privacy mode disabled: > **[Cursor – Getting a Request ID](https://docs.cursor.com/troubleshooting/request-reporting#how-do-i-find-a-request-id%3F)** > > Learn how to find and share request IDs in Cursor for better technical support and issue reporting ---
**Author:** ![jiezhonghu](https://avatars.discourse-cdn.com/v4/letter/j/779978/32.png) [@jiezhonghu](https://forum.cursor.com/u/jiezhonghu)\ **Post date:** [July 1, 2025, 7:21am UTC](https://forum.cursor.com/t/persistent-tool-call-timeout-issues-in-cursor-ai/50861/8 "2025-07-01T07:21:09Z")
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](https://us1.discourse-cdn.com/cursor1/original/3X/3/0/303a65e89e97363cefe851f18f3a04f55fa1d3c1.png) ---
**Author:** ![vivekrastogi799](https://avatars.discourse-cdn.com/v4/letter/v/eb8c5e/32.png) [@vivekrastogi799](https://forum.cursor.com/u/vivekrastogi799)\ **Post date:** [August 8, 2025, 7:35am UTC](https://forum.cursor.com/t/persistent-tool-call-timeout-issues-in-cursor-ai/50861/9 "2025-08-08T07:35:24Z")
Hello dan, please find the request ID. Facing this issue frequently - 246e3e2f-4ae3-4dd4-b238-88def50c7530 email - [vivek.rastogi@naukri.com](mailto:vivek.rastogi@naukri.com) ---
**Author:** ![Michael\_Gussert](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@Michael\_Gussert](https://forum.cursor.com/u/Michael_Gussert)\ **Post date:** [December 10, 2025, 11:51pm UTC](https://forum.cursor.com/t/persistent-tool-call-timeout-issues-in-cursor-ai/50861/10 "2025-12-10T23:51:48Z")
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](https://forum.cursor.com/uploads/short-url/9IKcN9aJF2KyVe9yCV54CUkAoJ8.txt) (37.9 KB) ---
**Author:** ![Harry\_Potter](https://avatars.discourse-cdn.com/v4/letter/h/a587f6/32.png) [@Harry\_Potter](https://forum.cursor.com/u/Harry_Potter)\ **Post date:** [January 13, 2026, 9:47am UTC](https://forum.cursor.com/t/persistent-tool-call-timeout-issues-in-cursor-ai/50861/11 "2026-01-13T09:47:00Z")
This is still an issue! It’s really frustrating. This never happened when I use copilot 💔 ---
**Author:** ![shyeon](https://avatars.discourse-cdn.com/v4/letter/s/5e9695/32.png) [@shyeon](https://forum.cursor.com/u/shyeon)\ **Post date:** [January 26, 2026, 1:19pm UTC](https://forum.cursor.com/t/persistent-tool-call-timeout-issues-in-cursor-ai/50861/12 "2026-01-26T13:19:38Z")
i fix similar problem fromt set ‘trust mode’ for current folder directory