Reverting changes does not reset the context

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Going back to a previous prompt in a chat correctly reverts changes made to the files, but the AI still remembers the rest of the conversation.

Steps to Reproduce

I went down a rabbit hole chasing a bug that showed up after it fixed an unrelated issue, and when realised the context was full and impacting performance, I went back to the prompt that started the rabbit hole and asked it to clean up the logs, with the intention of starting again from a clean chat. But it remembers the rest of the chat and starts going down the same rabbit hole again, even though none of it was mentioned anywhere above the prompt in question.

Expected Behavior

The context should revert to the state it was at the point of the conversation the user reverted to.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.34
VSCode Version: 1.105.1
Commit: 643ba67cd252e2888e296dd0cf34a0c5d7625b90
Date: 2026-01-10T21:17:10.428Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

GPT-5.2 High

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. The issue where a checkpoint rolls back files but the AI still remembers the later conversation is a known bug, and the team is investigating it.

Related reports: Editing a previous chat message in agent mode wipes work without warning

For now, please try:

  • Instead of rolling back, use Duplicate Chat (three dots on the message → Duplicate Chat). This creates a branch from that point without losing context
  • Start a new chat (Cmd+N) if you need a clean context
  • Use /summarize in chat to compress the chat history
  • Commit with Git before big experiments. Checkpoints don’t replace version control

I’ll pass this to the team so it can be prioritized.

Hi Dean, your first paragraph shows you understood the issue, but I wonder what happened with the rest. Is that an automated addition (that utterly failed to understand the issue), or… are you an instance of Sam the support bot?

Fair point. Sorry for the inaccuracy in my previous reply. Workarounds really don’t solve this specific issue. And no, I’m a real person, that’s exactly why I made a mistake.

You’re right. The expected behavior is that when you roll back a checkpoint, the AI context should also reset to that point. Right now that doesn’t happen, and it’s a design bug in the feature.

The team is already aware of this issue.

Haha, sorry for being suspicious, I guess dealing all day long with AIs that derail due to context saturation has biased my perception. :sweat_smile:

Anyway, thanks for responding!

1 Like

This is indeed a very serious issue.

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.