Cursor Forgot Everything Mid-Chat (Context Loss in Long Sessions)

Symptoms

• Deep into a long chat, Cursor suddenly behaves like a brand-new conversation.
• It cannot recall decisions made minutes earlier and gives random or contradictory answers.
• It re-reads documentation it already reviewed.
• All chat and agent history disappears after an update, reload, or computer restart.

Why it happens

Sessions have a finite context cap

As a long session approaches the model's context cap, Cursor summarizes and prunes earlier turns, compressing earlier reasoning into lossy notes that can drop out mid-response.

No cross-session memory

There is no memory across chats and no API to search past conversations, so anything not persisted to files is gone when the chat is.

Updates and reloads can wipe history outright

Forced app updates and reloads have bugs that wipe active session context and entire chat histories (forum threads 148192, 136644, 162904).

How to fix it

1. Start a fresh chat the moment quality degradesTreat chats as disposable: one task per chat. When Cursor starts contradicting itself or re-reading documentation it already reviewed, that session's useful life is over; a fresh chat outperforms an argument with a degraded one.
2. Persist state outside the chatKeep decisions and conventions in .cursor/rules and a plan or notes markdown file in the repo. Have the agent re-read them at the start of each chat, so memory lives on disk where nothing can prune it.
3. Re-attach what matters with @file and @folderDo not assume the agent still remembers code from earlier in the session. Explicit @file and @folder references put the current content back into context.
4. Copy irreplaceable chat content out before updatesForced updates and reloads have wiped active session context and entire chat histories (forum threads 148192, 136644, 162904). If a chat contains something you cannot recreate, copy it out of Cursor before updating or restarting.
5. Watch the context indicator and summarize to a file firstOn long sessions, watch the context indicator and write your own summary to a file before automatic pruning does it lossily. Commit working code frequently so a context-lost agent cannot talk itself into re-breaking things it no longer remembers building.

How to prevent it

• One task per chat, always.
• Keep .cursor/rules and a repo notes file as the source of truth for decisions, not the chat scrollback.
• Commit frequently so no working state depends on what the agent remembers.
• Before mandatory updates or reloads, copy anything irreplaceable out of the chat.

Frequently asked questions

Sources

• Cursor forum: Critical bug, AI session context loss during mandatory updates (thread 148192)
• Cursor forum: Why does Cursor keep losing context and giving random answers
• Cursor forum: Context dropout mid-response
• Cursor forum: Urgent, lost all chat and agent mode history (thread 136644)

Related errors