Must have been added recently..
The build key does nothing, plans are just useless now…
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.19045
example: c24baac9-9412-45bc-813c-c01967b32e75
happens with gpt 5.1 codex only because it saves to user folder? idk gpt 5.1 codex is unusable tbf
deanrie
(Dean Rie)
December 5, 2025, 7:05pm
3
Hey, thanks for the report. This is a known regression in 2.1.47-2.1.48 on Windows affecting Plan Mode: Build doesn’t trigger and plans may be saved outside the workspace.
Details and tracking:
What to try now:
Ask the agent in chat to build the plan via text instead of clicking Build
Launch with extensions disabled: cursor --disable-extensions
Check if a plan file appeared here: C:\Users\<User>\.cursor\plans and, if needed, move it manually to <workspace>\.cursor\plans
Could you send:
Exact repro steps
Errors from Help > Toggle Developer Tools > Console after clicking View Plan and Build
Confirm whether it reproduces on another model besides GPT-5.1 Codex
Additional Request IDs from chat for failed attempts
Let me know if the workarounds help.