Create Plan tool call errored or timed out

Bug Reports
1

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

5 Likes
2

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

3

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

1 Like
4

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
image1586×1626 314 KB

1 Like
5

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.

2 Likes
6

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

551c5103-9004-4101-8926-03084c32811b

image
image1604×786 50.4 KB

1 Like
7

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

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

image
image1410×530 42.2 KB

1 Like
8

Same issue here. 2.1.36

9

Same error in Version: 2.1.39 (Universal)

10

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

11

Create plan, also times out here.

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)
12

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

13

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

14

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