2.1.47 plans are always innaccessible and unreachable and cannot build

[StubFeed]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

since this new update : each plan made are not accessible and cannot be built

ERR Error: Unable to resolve resource c:%5CUsers%5Cjohn_%5C.cursor%5Cplans%5Cfix_p%26l_exchange_mismatch_7be62eb1.plan.md
at Roo.doCreateReferencedObject (workbench.desktop.main.js:6987:29305)
at Roo.doCreateReferencedObject (workbench.desktop.main.js:6987:29266)
at async Znr.acquire (workbench.desktop.main.js:47:2805)
at async ■■■.createModelReference (workbench.desktop.main.js:6987:31423)
at async Z1e.resolve (workbench.desktop.main.js:781:19645)
at async E1s.setInput (workbench.desktop.main.js:6475:91843)
at async brs.doSetInput (workbench.desktop.main.js:784:64237)
at async brs.doOpenEditor (workbench.desktop.main.js:784:61978)
at async brs.openEditor (workbench.desktop.main.js:784:60903)
at async workbench.desktop.main.js:2260:36791

Steps to Reproduce

plan mode, any plans made

Expected Behavior

I’m expecting to be able to view, edit and hit build like before this version

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.47 (system 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

For AI issues: which model did you use?

opus, composer…

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[deanrie]

Hey, thanks for the report.

I need more details to fix this quickly:

• Does the file exist at the path from the error? Check .cursor\plans and send a file list/screenshot (can you see fix_p&l_exchange_mismatch_7be62eb1.plan.md).
• Try creating a new plan with a simple name (only Latin letters/numbers, no &/%/spaces). Does it open/build?
• Back up and delete the .cursor\plans folder, restart Cursor, create a new plan - let me know if that helps.
• Open Help > Toggle Developer Tools > Console, reproduce the issue, and send the full log/screenshot with errors.
• If Build calls the model, share the Request ID for that attempt (how to get it: Getting a Request ID | Cursor Docs).

Also, clarify the exact steps you use to open the plan (from the plans list / from chat / Build button).

[FSama]

I have the same issues. I opted for the nightly update and updated to 2.2.0-pre.23.patch.0 but the issue remain. @deanrie to answer your questions:

• Trying “Save to workspace”… “The editor could not be opened due to an unexpected error. Please consult the log for more details.” and the file is not created
• My plan name is in latin “fix_migration_admin_totals_ce1c2c75.plan.md”
• Tried to delete the .cursor\plans folder, restarted Cursor, created a new plan… nothing changed!

These are the logs from the developer tools console:

workbench.desktop.main.js:55 ERR pk: Unable to resolve filesystem provider with relative file path ‘c:\Users\TailorMETA\.cursor\plans\fix_migration_period_totals_ce1c2c75.plan.md’
at Yko.withProvider (vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9397:87239)
at Yko.doWatch (vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9397:100513)
at vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9397:100196
at Yko.watch (vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9397:100265)
at Object.fn (vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6454:9248)
at E4a (vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:30058)
at Lnt (vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:29812)
at fAt (vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:31439)
at dDd (vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:32841)
at vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:32301
at yz (vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:31617)
at cDd (vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:32294)
at yz (vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:31628)
at q (vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:25976)
at U (vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:25946)
at vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:26809

workbench.desktop.main.js:6454 [ComposerCreatePlanToolCallBlock] Failed to load plan: pk: Unable to resolve filesystem provider with relative file path ‘c:\Users\TailorMETA\.cursor\plans\fix_migration_period_totals_ce1c2c75.plan.md’
at Yko.withProvider (vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9397:87239)
at Yko.withReadProvider (vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9397:87481)
at Yko.readFile (vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9397:92253)
at $is.loadPlanByUri (vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:636:679)
at async Gis.getPlanByUri (vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:648:2710)
at async vscode-file://vscode-app/c:/Users/TailorMETA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6454:8648

workbench.desktop.main.js:55 ERR Error: Unable to resolve resource c:%5CUsers%5CTailorMETA%5C.cursor%5Cplans%5Cfix_migration_period_totals_ce1c2c75.plan.md
at pso.doCreateReferencedObject (workbench.desktop.main.js:7313:29305)
at pso.doCreateReferencedObject (workbench.desktop.main.js:7313:29266)
at async Fnr.acquire (workbench.desktop.main.js:47:2805)
at async vso.createModelReference (workbench.desktop.main.js:7313:31423)
at async w1e.resolve (workbench.desktop.main.js:841:21613)
at async n1s.setInput (workbench.desktop.main.js:6797:91863)
at async Cas.doSetInput (workbench.desktop.main.js:844:64218)
at async Cas.doOpenEditor (workbench.desktop.main.js:844:61959)
at async Cas.openEditor (workbench.desktop.main.js:844:60884)
at async workbench.desktop.main.js:2340:36791
at async Gis.openPlanInEditor (workbench.desktop.main.js:647:2191)

[FSama]

For me, the only thing that worked right now was downgrading to 2.1.46.

[deanrie]

Hey, thanks for the details - looks like a regression on Windows in 2.1.47/2.2.0-pre.23 (errors “Unable to resolve resource …” and “Unable to resolve filesystem provider with relative file path”). I’ve passed it to the engineers and we’re working on a fix.

For now, as a temporary solution - rollback to 2.1.46 (confirmed by @FSama).
We’ll keep you updated in this thread.

[mehmet-py (xenit)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I type build in the chat, I see this error appear in the terminal. I press the button, but nothing is processed.

Steps to Reproduce

workbench.desktop.main.js:2890 [ComposerPlanService] Failed to load plan content from file: mk: Unable to resolve filesystem provider with relative file path ‘c:\Users\Mehmet.cursor\plans\owl-avatar-system_8eea6e6f.plan.md’
at $xo.withProvider (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8929:87375)
at $xo.withReadProvider (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8929:87617)
at $xo.readFile (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8929:92389)
at kms.loadPlanByUri (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:2884:679)
at async Ems.acceptPlan (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:2890:4230)

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.47 (system 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

For AI issues: which model did you use?

auto

For AI issues: add Request ID with privacy disabled

f8901d8a-d5a4-4e91-ab11-f4c27c04837b

Does this stop you from using Cursor

No - Cursor works, but with this issue

[StubFeed]

the file do get saved.

if I browse manually in windows explorer, I can open it in text editor…

but cursor says unexpected error and don’t open it

[andrewh (Andrew Milich)]

Looking into this

[neolu]

Same issue also with WSL! Stops me from using Cursor and took me 5% of my monthly usage

[andrewh (Andrew Milich)]

Fix is coming shortly

[StubFeed]

The only way around I found right now

is to add C:\Users\(username)\.cursor\plans into my workspace and when the plan is fully generated it appears there, so I can manually open it and hit build

[neolu]

Did you fix it?

[FSama]

You released two consecutive versions with a critical bug that renders the system unusable. And the update wasn’t one of those early or nightly ones. Two days later, thousands of paying users are still waiting for a solution!

[andrewh (Andrew Milich)]

Could you try updating to 2.1.49? This should fix it

[goiltpatpat (ZeonLight)]

Great, it’s been fixed

[andrewh (Andrew Milich)]

Glad to hear - 2.1.49 should improve plan stability a lot.

[NewCoder891 (VibeCoder89)]

Yes, i had the same problem. but it is fixed now I guess!
Cursor please make your health checks before pushing updates.
It really happens on very often now that features are broken after updates… that ■■■■■…