Cursor remembers none of chat context (even on second message)

Bug Reports
1

Cursor now remembers none of my chat context.
You can see in the below picture that in my second message, it hasn’t even remembered the first.

Can anyone help please?

Cursor_25_01_24_20h_44m30s738ms
Cursor_25_01_24_20h_44m30s738ms1439×1259 84.6 KB

2

Hmm, that’s weird. I can’t reproduce it. Is the “Current file” very long by any chance?

3

I think I’ve found the cause…

My ‘rules for AI’ is 3,368 words :grin:.

Ideally, I’d like it to be able to handle both the ‘rules for AI’, and the chat context. But if it can’t, I’d like it to tell me, and let me choose.

4

Thank you for the update. Yea, that shouldn’t happen. We’ll have a look.

1 Like
5

@Jakob if I reduced line breaks, so the doc was on less lines, would the AI be able to handle it better?

e.g.
Before - rules for AI
I use React
I use Node.js
…

After - rules for AI
I use React|I use Node.js
…

6

No, removing new lines reduces the token size of your text only very slightly. You can try here.

I would try to keep only the most essential things in your Rules For AI and move some stuff to Custom Docs.

1 Like
7

If your chat cursor isn’t retaining any context between messages, here are some potential causes and solutions:

  1. Session Management: Ensure your chat app’s session management is correctly implemented. If each message starts a new session, it won’t remember the previous context. Check if there’s a way to retain the session ID for continuity.
  2. State Management: In frameworks like Flutter, proper state management (e.g., using Provider, Bloc, or Riverpod) can help preserve data between messages. Verify that your state solution supports the chat flow and keeps context.
  3. Backend Configuration: If your app interacts with a backend, ensure the server maintains a conversation history between messages. Issues in API configuration or authentication can sometimes reset sessions.

These steps should ensure your chat cursor maintains context across messages.