I lose my context after reloading cursor,and I have just discussed a nice plan for many hours and ready to play ,But Cursor lagged a bit, so I reload it and when I reopened it, there was no history or context left — only my very first question still sitting in the input box, waiting to be sent.
I remember last time I do this when I back the context still there.
That’s bad.
Hey, this is a known issue. If you reload or Cursor closes unexpectedly, especially after it’s been running for a long time, part of the chat history might not get written to disk in time and can be lost. It’s a bug on our side, we’re tracking it, but I can’t share a fix timeline yet.
Workaround for next time: instead of reload, close Cursor via File > Exit or fully close the window, then reopen it. With a graceful close, the state is saved to disk correctly.
Unfortunately, it’s probably not possible to restore the context that was already lost from this session, since the unsaved data didn’t get written. If you notice history disappearing even after a normal close, share your Cursor version and OS and we’ll take a closer look.
But I did close and reopen Cursor normally, and later I just found half of that record in the cache,the first half.
Thanks for clarifying. The fact that only the first half is left in the cache is an important detail. It looks like during a long session, part of the state didn’t finish writing to disk, even though the app closed normally.
To take a closer look, can you share:
- your Cursor version (Help > About or Cursor > About Cursor)
- your OS and OS version
Also, was that chat very large, like many hours of work in one thread? That’ll help us tell if we’re hitting session size limits.
For now, until this bug is fixed, for long important plans it’s best to save key points somewhere else from time to time, like in a file in the project, so you’re not relying only on auto-save of the state.
Version: 3.7.36 (user setup)
VS Code Extension API: 1.105.1
Commit: 776d1f9d76df50a4e0aeca61819a88e7c1b861e0
Date: 2026-06-13T00:31:56.287Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200
But I don’t quite remember whether I did a long session of work or not.
Thanks for the details. I’ve noted the version and OS.
The fact that only the first half of the chat remained even after a normal close most likely means that in a long session, part of the state didn’t finish writing to disk. This is the same known issue with saving history. It’s a bug on our side, we’re tracking it, but I can’t share an ETA for a fix yet.
For now, a tip for the future. If you’re working on important long plans, copy key points into a separate file in the project from time to time, so you’re not relying only on auto-saving state. Also, when possible, close Cursor via File > Exit instead of reload.
If you notice history disappearing even in short sessions, let me know and we’ll take a closer look.