"Plan mode is active" / message did not include <end_plan_mode/>

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I cannot run build after creating a plan in plan mode. The plan mode is NOT active (agent mode is), but the LLM still tells me the plan mode is active.

Steps to Reproduce

No idea. it is fragile

Screenshots / Screen Recordings

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.44
VSCode Version: 1.105.1
Commit: 20adc1003928b0f1b99305dbaf845656ff81f5d0
Date: 2025-12-24T21:41:47.598Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.5.0-44-generic

For AI issues: which model did you use?

GPT-5.2

For AI issues: add Request ID with privacy disabled

e926a069-4fe7-4f22-85b1-2f6d5f668f31

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @klntsky

Thanks for reporting this. We already have this exact bug filed in our system, and I’ll link your report to it. It was also reported here:

In the meantime, the agent is right. If you reply <end_plan_mode/> in the chat, you should be able to move on.

Dealing with the same issue across the 5.2 models. It also seems to be able to create a plan, but then it can’t access it:

Got it. Next I’ll locate the authoritative workdoc todos.md for this feature, set the first task to in_progress, then implement the three code changes (Apps Script payload, Cloud Run creds selection, README docs) and keep todos.md/log.md updated after each milestone.

I’m not seeing a workdocs folder/todos for this new “netsuite_instance” feature yet (nothing matches netsuite_instance under doc/workdocs). Next I’ll search the repo for the todo IDs from the plan (netsuite-instance-*) and, if they truly don’t exist, we’ll need to create the correct doc/workdocs/2025-12-29-netsuite-instance-creds/ structure before any code edits.

Blocker before I can start coding (workdocs-first)

I searched doc/workdocs/**/todos.md and the repo for the plan todo IDs (netsuite-instance-payload, netsuite-instance-cloudrun-creds, netsuite-instance-docs) and they don’t exist anywhere in the workspace right now.

To follow your “workdocs-first” rule (and your instruction to mark the first todo in_progress before edits), I need one clarification:

Where are the authoritative todos for this feature?

a) Create a new workdocs folder doc/workdocs/2025-12-29-netsuite-instance-creds/ and add those 3 todos there (then I’ll start implementing immediately)

b) They already exist—tell me the exact folder path (e.g. doc/workdocs/.../todos.md) and I’ll use that

Then after trying to give it the path for the plan:

I can’t use {I redacted path name} as the authoritative task tracker (per your Workdocs‑First rules), and I also cannot find the three plan todo IDs anywhere under doc/workdocs/**/todos.md.

To proceed correctly (and to be able to mark the first task in_progress before any code edits), answer this:

Where should the authoritative tasks live?

a) Create doc/workdocs/2025-12-29-netsuite-instance-creds/ and import the 3 todo IDs from the plan into todos.md (plus a plan.md snapshot copy of the plan text)

b) They already exist in a workdocs folder—paste the exact path to that folder’s todos.md

Then I go grab the markdown text from finder:

I’m still in Plan mode per the system guardrails, so I can’t touch code yet. Next I’ll create the authoritative workdocs folder for this feature and write plan.md + todos.md from the plan you pasted (with the 3 IDs exactly), then I’ll ask you for the <end_plan_mode/> signal so I can start implementing and mark the first todo in_progress.

Just being verbose in the spirit of engineering bug fixing.

Repro steps:

  1. Ask it to plan with 5.2
  2. Switch to agent mode
  3. Click ‘build’ near the plan widget