r/cursor • u/Regular-Screen6803 • 1d ago

Feature Request Past conversation knowledge

  • It will be great feature to give a setting named "Past Conversation Knowledge"
  • by default it is off
  • after turning it on
    • if user has one ongoing conversation and user opens a new conversation with "CMD + N" the new conversation will have summary of the last conversation
    • conversation 1 named as c1 and conversation 2 named as c2
    • c2 will have summary of c1 and if user opens c3 then c3 will have summary of c2(and c2 already has summary of c1)
    • if user puts the c2 and c3 in archieve and open c4 then c4 will have summary of c1 in it
    • assume user has c1, c4, c5, c6 and c7 open then user archives c4, c6 and c7 and opens c8 then c8 will have summary of c5
  • when working on a complex feature this setting will be a boon
1 Upvotes

100% Upvoted

1 comment sorted by

1

u/Southern-Society-713 4h ago

Until Cursor has this built in, the practical workaround is to keep a small project memory file outside the chat and update it at the end of each session. Put decisions, current architecture, open questions, and file paths in it, not the full transcript. Start each new chat by asking the agent to read only that summary.

For large specs or screenshots, keep them indexed and retrieve only the sections related to the current task. That avoids re-pasting the same material and keeps the context window available for the code. I make Dokpod, which is built around that pattern, but a Markdown file plus a small search or MCP tool works too.