Remix.run Logo
Ask HN: How do you handle long-term memory with AI tools like Cursor and Claude?
3 points by JakaKotnik 8 hours ago | 1 comments

I keep running into the same friction point when coding with AI tools. They are amazing inside a single session, but the moment you open a new one, they forget everything about the project, past reasoning, edge cases, or architecture notes.

I know some people maintain MD files or detailed RAG setups, but most developers I talk to say their context is scattered across Slack, GitHub issues, Notion, docs, emails, etc.

So I’m curious how others solve this today:

• Do you rely on project-local markdown files? • Do you manually restitch context every session? • Have you built your own external memory store? • Or do you just accept that AI will forget most things between sessions?

Not trying to promote anything. I genuinely want to understand whether this is a real pain point across teams or just a “me” problem.

Would love to hear how you manage long-term context in your workflow.

dtagames 8 hours ago | parent [-]

In short, MD files. After stuff works, I canonize the documentation about how it works by having Cursor write all of that in a special folder. Then, I can @reference that folder or a doc in it at the start of a prompt that will need that context.

It's part of a larger process for working with LLMs that I call "Plans on Plans." I wrote about it on Medium.[0]

[0] https://levelup.gitconnected.com/you-are-bugs-improving-your...