Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Cursor IDE Describe the Bug This bug has come up a lot. Cursor becomes detached from its memories and starts going off-script which results in a lot of wasted prompts. Trying to get Cursor to access memories during these times results in “tool update_memory not found"
Sometimes it depends on the agent, other times not. It definitely happens with Composer 1, less so with Claude Sonnet. This bug has been reported a lot but is always either ignored completely or “we’ll look into it” and ignored. One could assume that the bug isn’t being fixed because it’s not in Cursor’s best interests to fix something that results in wasted prompts. Does Cursor actually intend on looking into this bug at some point?
Steps to Reproduce
In Composer 1, try to add a new rule or memory, especially after or during Plan mode
Expected Behavior
Should be adding a rule / memory and shouldn’t be disconnected from the update_memory tool
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.0.77 (Universal)
VSCode Version: 1.99.3
Commit: ba90f2f88e4911312761abab9492c42442117cf0
Date: 2025-11-13T23:10:43.113Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0
For AI issues: which model did you use?
Composer 1, Sonnet 4
Does this stop you from using Cursor
No - Cursor works, but with this issue