Plan mode "build" not working in chat

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When i use plan mode , the click on the “build” button in chat don’t work and i can’t see the plan : “The editor could not be opened due to an unexpected error. Please consult the log for more details.”. 3 times in last 5 minutes.

Steps to Reproduce

build a plan with plan mode and try to execute it in chat. IDE

Expected Behavior

something i can’t see the plan and the button with “build” do nothing when i click on it.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.47 (user setup)
VSCode Version: 1.105.1
Commit: 2d3ce3499c15efd55b6b8538ea255eb7ba4266b0
Date: 2025-12-04T02:31:50.567Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

11 Likes

I just asked Cursor to plan and it showed the same message after planning when I try review the plan: “The editor could not be opened due to an unexpected error. Please consult the log for more details”

2 Likes

I’m having the same issue.

1 Like

Same error here, any fixes?

Same error here. If it works (sometimes) and the IDE creates a file, I cannot accept it. The “ACCEPT” button is gone and the chat is stuck then.

I see the same message but the plan is built if a text prompt to build the plan is issued

Hey, thanks for the report. We’re seeing a few cases like this today on 2.1.47, mostly on Windows. We’re already looking into it.

For now, as a temporary workaround: try asking to build the plan with a text prompt in the chat instead of the Build button - a few users reported that the plan builds that way.

Let me know if the workaround helps.

2 Likes

The same on Mac, 2.1.47

1 Like

Cursor also freezes randomly. Windows 11. This was fixed in a prior release and now I regret clicking “Update Now”

Can we get better changelogs for these frequent updates that seemingly break things entirely? When this occurs, our team still gets charged for these failed requests. @deanrie

This is an AI-first product and those changelogs should be largely automated at this point. If I click update, I should have a reasonable understanding of what is changing as I update.

Thanks. I’ve already passed the Build-in-Plan issue to the team.

For the freezes on 2.1.47, we need more details to finalize the fixes:

  • Exact repro steps and OS/Cursor version (Help > About)
  • A screenshot or video of the freeze
  • What Developer: Open Process Explorer shows during the freeze
  • Try running cursor --disable-extensions and tell us if behavior changes
  • Any errors from DevTools Console

For charges on failed requests, please send the Request IDs (in chat: top-right menu > Copy Request ID).

Got the note about changelogs - I’ll pass it to the team and we’ll try to make them more informative.

Here’s some immediate information @deanrie NOTE: I won’t be able to provide screenshots or videos on a public forum. I can submit them to support, if needed, but need help on how to do that appropriately.

  1. Any time the window focus changes away from Cursor (to Edge or another browser), the freeze is much more likely to occur.
  2. See note above, screenshots or videos will be difficult to provide.
  3. Developer: Open Process Explorer - this is impossible since the entire application is frozen. The window is unable to be interacted with, and the window doesn’t even come to the front any longer. Nothing works. I have to use Task Manager → Process Kill to solve. This is more likely to occur when the agent/plan modes look to edit a file (plan file or agent based changes to files the agent needs to make) while the window is NOT in focus
  4. I can try running cursor –disable-extensions, but I don’t feel it’s an extension issue because the only changes have been with the frequent IDE Updates (which again, provide no release notes to determine what has changed.)
  5. DevTools, See above. If there’s a way to enable debug logging to provide stack traces or something else ahead of a freeze, that’d be helpful.

Same problem here, plus, the agent mode with the browser is causing the antivirus to interpret it as an attack and quarantine Cursor.exe.

same issue

Version: 2.1.47 (user setup)
VSCode Version: 1.105.1
Commit: 2d3ce3499c15efd55b6b8538ea255eb7ba4266b0
Date: 2025-12-04T02:31:50.567Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

1 Like

Same here on Mac with Cursor version 2.1.47

Same issue as others.

Version: 2.1.48 (user setup)
VSCode Version: 1.105.1
Commit: ce371ffbf5e240ca47f4b5f3f20efed084991120
Date: 2025-12-04T19:26:27.263Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100

We’re looking into the plan mode issue. For antivirus info - you may have to mark Cursor manually as safe. The browser feature should be unrelated, but more info would be helpful.

1 Like

I am also not able to run any commands during cursor execution.

+1, happening to me on WSL. Can’t do anything with auto or composer, interestingly enough GPT-5.1 Codex Max will show the accept buttons (even though I don’t want to manually approve each file edit).

Version: 2.1.48 (user setup)
VSCode Version: 1.105.1
Commit: ce371ffbf5e240ca47f4b5f3f20efed084991120
Date: 2025-12-04T19:26:27.263Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100

Same issue here. 2.1.47 and 2.1.48

yes same here since yesterday, even save to workspace showing this error, so my temporary fix is to tell the grok (free version) to move it to workspace.