While using /commands, a new chat acted on instructions that were never given in that chat. Cursor’s own output said:
“You’re right to press this. Here is exactly what drove that external-repo fetch, from the message payload I received in this chat. In the cursor_commands block of that earlier turn, this text was present (verbatim):”
It then showed old instructions (including an external-repo fetch) that came from earlier, separate chats, not from the current one.
What I expected:
A fresh chat should only execute what I type in that chat.
cursor_commands and similar metadata should not resurrect instructions from other chats.
What actually happened:
In a new / run, Cursor pulled in old cursor_commands content and treated it as actionable.
I saw this happen in multiple chats, separated by hours, not just once.
Why this is a problem:
It looks like cross-session context/caching leakage.
It can cause unintended actions (like hitting external repos) in a chat that never asked for them.
It undermines trust that each new chat is isolated.
Request:
Treat only the latest explicit user message in the current chat as actionable by default.
Do not execute anything from cursor_commands (or similar metadata) unless I clearly ask for it in this chat.
Please investigate possible cross-chat caching or payload mixing that reuses cursor_commands from other sessions.
Steps to Reproduce
Check your patch notes to see what you broke this time?
Expected Behavior
A fresh chat should only execute what I type in that chat.
cursor_commands and similar metadata should not resurrect instructions from other chats.
Hey, thanks for the report. This looks like a session isolation issue. A cursor_commands metadata leak between separate chats is definitely not expected behavior.
To help the team investigate, could you share:
The Request ID from the session where this happened (chat menu in the top-right corner → Copy Request ID).
A bit more detail on the sequence: roughly what was in the original chat, and what showed up unexpectedly in the new one? Also, were the chats in the same project/workspace, or in different ones?
As a temporary workaround that might help, try fully closing the chat panel (not just starting a new chat) before opening a new one.
I reviewed the recommended report about people having issues with cursor not respecting the mode it’s given ask/plan/agent. I’ve come across that while working with cursor, this is something complete different.
More Detail:
All this transpired in a single project with no direct relationship with another project. (I did have another project open, i dont’ think i interacted with it during this time frame at all.)
I noticed after opening a new chat and trigger one of my /commands, that directions/information were being injected from previous chats. The main way i noticed it, was it kept reading a repo i asked about in 3-5 chats ago. I also noticed something i asked in about 30-40 chats ago. That’s when i inquired for it to tell me where that info came from. It gave me the “Factual Payload” and i noticed there was 3 messages included in this payload were the starting messages from 3 different chats.
After making this report and trying to ask Cursor to clear the issue <haha, right?> each continued chat had issues were the starting chat had cached items from other chats that complete interfered with what i was asking.
This caused me to have to stop using cursor for the night.
–
I tried to close the chat by clicking the 3 dots, and clicking on “Close chat” nothing happens. Ctrl + W does work. That just closes a chat window. Are you asking me to manually close all my chats or to toggle the whole chat window?
