# Create Plan tool call errored or timed out

**URL:** <https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959>\
**Category:** Bug Reports\
**Created:** [November 24, 2025, 6:03pm UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959 "2025-11-24T18:03:15Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mrk-Han](https://avatars.discourse-cdn.com/v4/letter/m/c77e96/32.png) [@Mrk-Han](https://forum.cursor.com/u/Mrk-Han)\
**Post date:** [November 24, 2025, 6:03pm UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959/1 "2025-11-24T18:03:16Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

Editing and creating plans is still quite buggy. I’m often getting “create plan tool call errored or timed out”

### Steps to Reproduce

Create a plan then edit it in plan mode (I was using composer 1)

### Expected Behavior

Plans are edited when given feedback on them

### Operating System

MacOS

### Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.26  
VSCode Version: 1.105.1  
Commit: f628a4761be40b8869ca61a6189cafd14756dff0  
Date: 2025-11-24T05:39:06.655Z  
Electron: 37.7.0  
Chromium: 138.0.7204.251  
Node.js: 22.20.0  
V8: 13.8.258.32-electron.0  
OS: Darwin arm64 24.4.0

### For AI issues: which model did you use?

composer 1

### Additional Information

One of the most important features of cursor 2.x, can’t use it without this working

### Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [November 25, 2025, 11:05am UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959/2 "2025-11-25T11:05:13Z")

</div>

Hey, thanks for the report. This is a known regression in Planning Mode that started in version 2.1.0 and is affecting multiple users. The team is already aware and investigating.

To help link your case, could you please share the Request ID from a failed planning attempt?

Chat menu (top right) → Copy Request ID

We’re tracking this issue here: [Planner broken in 2.1.0](https://forum.cursor.com/t/planner-broken-in-2-1-0/143287)

---

<div class="post-metadata">

**Author:** ![Mrk-Han](https://avatars.discourse-cdn.com/v4/letter/m/c77e96/32.png) [@Mrk-Han](https://forum.cursor.com/u/Mrk-Han)\
**Post date:** [November 25, 2025, 3:02pm UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959/3 "2025-11-25T15:02:06Z")

</div>

I’ll attach future request IDs here, plan mode doesn’t give the same request ID option in the same spot ( and I didnt know it was in top right at all times )

Thank you

---

<div class="post-metadata">

**Author:** ![Mrk-Han](https://avatars.discourse-cdn.com/v4/letter/m/c77e96/32.png) [@Mrk-Han](https://forum.cursor.com/u/Mrk-Han)\
**Post date:** [November 25, 2025, 4:15pm UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959/4 "2025-11-25T16:15:28Z")

</div>

Still getting a bunch of received invalid string to replace in plan

76465a5e-56e4-4ffc-a9f7-0e3372e4ab10

Asked it to included sources in the plan, said it created a new plan but never did

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/2/f/2f60cddca00de5bc9d98facd0b1cfd4b7002cf49.png)

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [November 25, 2025, 4:22pm UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959/5 "2025-11-25T16:22:53Z")

</div>

Thanks for sharing the Request ID and the screenshot with the “invalid string to replace” error! This is really helpful for the team to track your specific case.

The “invalid string to replace” error is related to the same Planning Mode regression that’s currently being investigated. Your request has been linked to the tracking thread.

As a temporary workaround while the fix is in progress:

- Try starting a new plan for major changes instead of editing existing ones.
- If you’ve saved plans to `.cursor/plans/`, you can edit the markdown directly there.

The team is actively working on this issue.

---

<div class="post-metadata">

**Author:** ![Mrk-Han](https://avatars.discourse-cdn.com/v4/letter/m/c77e96/32.png) [@Mrk-Han](https://forum.cursor.com/u/Mrk-Han)\
**Post date:** [November 25, 2025, 4:25pm UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959/6 "2025-11-25T16:25:15Z")

</div>

Here’s the request ID and screenshot of “Create plan tool call errored or timed out”

551c5103-9004-4101-8926-03084c32811b

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/d/a/da6bfa8bb0a93f4231e5adf2cbcf79a0327c14b7.png)

---

<div class="post-metadata">

**Author:** ![Mrk-Han](https://avatars.discourse-cdn.com/v4/letter/m/c77e96/32.png) [@Mrk-Han](https://forum.cursor.com/u/Mrk-Han)\
**Post date:** [November 25, 2025, 4:46pm UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959/7 "2025-11-25T16:46:08Z")

</div>

09090e5c-96d0-435c-bc5e-aaec2000bac8

And here again: Create plan tool call errored or timed out

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/e/c/ecdc86b807d0455def66d35141da7ec32a136d0f.png)

---

<div class="post-metadata">

**Author:** ![rory](https://avatars.discourse-cdn.com/v4/letter/r/a183cd/32.png) [@rory](https://forum.cursor.com/u/rory)\
**Post date:** [November 26, 2025, 2:30pm UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959/8 "2025-11-26T14:30:16Z")

</div>

Same issue here. 2.1.36

---

<div class="post-metadata">

**Author:** ![Galler\_India](https://avatars.discourse-cdn.com/v4/letter/g/e56c9b/32.png) [@Galler\_India](https://forum.cursor.com/u/Galler_India)\
**Post date:** [November 27, 2025, 10:12am UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959/9 "2025-11-27T10:12:18Z")

</div>

Same error in Version: 2.1.39 (Universal)

---

<div class="post-metadata">

**Author:** ![alexandrosandre](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/alexandrosandre/32/8576_2.png) [@alexandrosandre](https://forum.cursor.com/u/alexandrosandre)\
**Post date:** [November 27, 2025, 1:56pm UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959/10 "2025-11-27T13:56:15Z")

</div>

Same here  
v2.1.39  
c7e867e9-ddb2-4fc6-9d5e-7b5edae63d68

---

<div class="post-metadata">

**Author:** ![master3395](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/master3395/32/46687_2.png) [@master3395](https://forum.cursor.com/u/master3395)\
**Post date:** [November 28, 2025, 9:51pm UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959/11 "2025-11-28T21:51:53Z")

</div>

Create plan, also times out here.

```auto
Request ID: dc52bf6d-75fa-4b11-a92a-8a14894a9b93
"{\"error\":\"ERROR_BAD_REQUEST\",\"details\":{\"title\":\"Bad request.\",\"detail\":\"Bad Request\",\"isRetryable\":false},\"isExpected\":true}"
ConnectError: [invalid_argument] Error
    at oNc.$endAiConnectTransportReportError (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6426:446069)
    at iDo._doInvokeHandler (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7047:22831)
    at iDo._invokeHandler (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7047:22573)
    at iDo._receiveRequest (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7047:21335)
    at iDo._receiveOneMessage (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7047:20152)
    at ODt.value (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7047:18244)
    at ke._deliver (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:49:2962)
    at ke.fire (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:49:3283)
    at hmt.fire (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6411:12156)
    at MessagePort.<anonymous> (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9179:18433)

```

---

<div class="post-metadata">

**Author:** ![zzest](https://avatars.discourse-cdn.com/v4/letter/z/82dd89/32.png) [@zzest](https://forum.cursor.com/u/zzest)\
**Post date:** [November 29, 2025, 11:27am UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959/12 "2025-11-29T11:27:40Z")

</div>

Same. Very disappointed in this regression, I was hoping to make headway over the weekend…

---

<div class="post-metadata">

**Author:** ![mmatiush](https://avatars.discourse-cdn.com/v4/letter/m/fbc32d/32.png) [@mmatiush](https://forum.cursor.com/u/mmatiush)\
**Post date:** [November 29, 2025, 11:29pm UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959/13 "2025-11-29T23:29:35Z")

</div>

Same issue. Looking forward to it being fixed.

The issue has been for a couple of weeks. Makes the development process wo much worse.

![CleanShot 2025-11-30 at 01.27.59](https://us1.discourse-cdn.com/cursor1/original/3X/d/4/d46c7e0e4aa4cc1242d7635670942c66da455fbf.png)

---

<div class="post-metadata">

**Author:** ![douglac](https://avatars.discourse-cdn.com/v4/letter/d/958977/32.png) [@douglac](https://forum.cursor.com/u/douglac)\
**Post date:** [November 30, 2025, 7:52pm UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959/14 "2025-11-30T19:52:46Z")

</div>

Same here. Sometimes I need to change model to make it works

---

<div class="post-metadata">

**Author:** ![Matt\_Raspberry](https://avatars.discourse-cdn.com/v4/letter/m/35a633/32.png) [@Matt\_Raspberry](https://forum.cursor.com/u/Matt_Raspberry)\
**Post date:** [December 1, 2025, 4:33pm UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959/15 "2025-12-01T16:33:17Z")

</div>

Same issue. Request ID `ac299494-7bd6-48a1-a3b1-87541a94b70d` in version ` 2.1.42`

---

<div class="post-metadata">

**Author:** ![Mike\_Watson](https://avatars.discourse-cdn.com/v4/letter/m/6de8d8/32.png) [@Mike\_Watson](https://forum.cursor.com/u/Mike_Watson)\
**Post date:** [December 2, 2025, 3:01am UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959/16 "2025-12-02T03:01:35Z")

</div>

I keep running into this too

---

<div class="post-metadata">

**Author:** ![apsoto](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/apsoto/32/76089_2.png) [@apsoto](https://forum.cursor.com/u/apsoto)\
**Post date:** [December 5, 2025, 6:49pm UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959/17 "2025-12-05T18:49:01Z")

</div>

This happens consistently after the initial plan. The initial plan creates consistently, but if I submit a follow up message in the chat with notes/comments/corrections to update the plan in plan mode, it happens fairly often

version:  
Version: 2.1.49 (Universal)  
VSCode Version: 1.105.1  
Commit: 21a2ed198584d56a91c0b996d1a09c93f8538440  
Date: 2025-12-05T07:49:06.016Z  
Electron: 37.7.0  
Chromium: 138.0.7204.251  
Node.js: 22.20.0  
V8: 13.8.258.32-electron.0  
OS: Darwin arm64 25.1.0

example request id  
3955221d-ebdb-4dff-8b43-a3f9fc0d5640

---

<div class="post-metadata">

**Author:** ![AltK-Ninja](https://avatars.discourse-cdn.com/v4/letter/a/e274bd/32.png) [@AltK-Ninja](https://forum.cursor.com/u/AltK-Ninja)\
**Post date:** [December 6, 2025, 3:20pm UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959/18 "2025-12-06T15:20:15Z")

</div>

Same here on 2.1.49

Request ID: c11db302-b278-4361-af53-8e384e1b7e37

Version: 2.1.49  
VSCode Version: 1.105.1  
Commit: 21a2ed198584d56a91c0b996d1a09c93f8538440  
Date: 2025-12-05T07:49:06.016Z  
Electron: 37.7.0  
Chromium: 138.0.7204.251  
Node.js: 22.20.0  
V8: 13.8.258.32-electron.0  
OS: Darwin arm64 25.1.0

---

<div class="post-metadata">

**Author:** ![Jerzy\_Jeszcze](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jerzy_jeszcze/32/89870_2.png) [@Jerzy\_Jeszcze](https://forum.cursor.com/u/Jerzy_Jeszcze)\
**Post date:** [December 7, 2025, 4:52am UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959/19 "2025-12-07T04:52:42Z")

</div>

yeah happened to me just yesterday, auto mode.

–// speculation only  
Funny how it always happen to the great improved plan that included a bit of “scenarios”. To me they just ban when you had a plan for something good that you could just feed to LLM to execute. “You just found a secret formula - so we will ban you and tell it’s LLM’s going retarded mode for fun effects”.

Try clearing cache, then use specific mode. Worked once.

SOLUTION THAT WORKED FOR ME - credits to author

> [@Cursor is unable to update a plan](https://forum.cursor.com/t/cursor-is-unable-to-update-a-plan/144277/5):
>
> when you get tool call errored, try to hover over the session tab and close it, possibility close all the sessions. then kill the cursor process from task manager, restart pc for sanity. open cursor and open the session from the list of recent sessions. This has been working with me, it might be superstitious solution, so far its been working 100% sucess rate! Good Luck!

---

<div class="post-metadata">

**Author:** ![k3vob](https://avatars.discourse-cdn.com/v4/letter/k/9e8a1a/32.png) [@k3vob](https://forum.cursor.com/u/k3vob)\
**Post date:** [December 8, 2025, 9:59am UTC](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959/20 "2025-12-08T09:59:39Z")

</div>

It’s honestly insane that this bug hasn’t been fixed for such a long time. This is literally one of the core features to Cursor, I don’t know how this wasn’t prioritised to be fixed ASAP weeks ago - IMO it absolutely should have been fixed within a few hours of the first report. Infuriating when this happens when you’re trying to plan a massive feature and have to start a new conversation just to get around this error. You even see it happening multiple times in [Theo’s (T3) recent YouTube video](https://www.youtube.com/watch?v=-g1yKRo5XtY) that has 100k views.

My workaround that usually works is to say something like “delete the entire existing plan file completely and write the plan to a new plan file again from scratch”.

[Next page](https://forum.cursor.com/t/create-plan-tool-call-errored-or-timed-out/143959.md?page=2)
