Hey, thanks for the report. What you’re describing is a bit different from the topic of this thread the one where the agent sticks to an old plan after context summarization, and you’ve already started a separate thread for it. Let’s keep the discussion there so we don’t get mixed up: Bare “continue” pulls ambient plan/workstream context despite User Rule. There’s already a reply from a teammate there.
In short: Cursor sends the agent ambient context open and recently viewed files, workspace state, active plan before User Rules are applied. Rules affect how the model behaves, but they don’t remove material that’s already been added to context, so the model can still reference ambient .cursor/plans.
Workarounds for now:
- Be explicit: use
continue <specific task>instead of plaincontinue. - Start a fresh chat and close unrelated
.cursor/planstabs when you need a clean continuation.