"Next Steps" Internal Memory Management Bugged

Describe the Bug

I had a long (multi hours long) agent conversation with Claude and it was decently persisting context.

Randomly, after a failed tool call for a powershell command, Claude completely forgot the previous last few messages and the context of our ongoing conversation.

I asked it to show me what was wrong, and it literally dumped its entire prompt (yes, the prompt with all the memories, and no it was NOT a hallucination). For obvious reasons, I won’t share it here, but its what I believe is the “generate prompt” basically the structured context.

That led me to discover two main issues in the context management I believe are bugs:

  1. “Next Steps Identified” was completely wrong. Its as if it had time-travelled hours back. The items here were long-past completed.
  2. The <deleted_files> </deleted_files> tag contents were also hours old. Its as if an old checkpoint had been internally incorrectly triggered.

This behavior of “forgetting where I am and what we were talking about” has happened in the past but this is the first time I’ve been able to diagnose the source of it because of the prompt-object output.

Steps to Reproduce

Hours-long conversation.

Expected Behavior

The expected behavior is for degraded context over hours-long conversations, not random forgetfulness and complete 180’s of personality.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.2 (user setup)
VSCode Version: 1.99.3
Commit: faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0
Date: 2025-07-07T06:19:13.016Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue