Nufar Gaspar

So what's currently a limitation in one tool will probably be solved by the next time you go and look into a new tool release.

So the question is, if so many experts are working on memory, what does it mean for you in practical terms?

So first, the good news, you can just lean on the existing memory in your tool and it will keep getting better for sure.

But at least as of now, no matter which tool you're using and how well its memory is working, there are a few things that you should do.

At the very minimum, I want you to understand how your tool's memory works.

You can ask it directly.

Explain how your memory system works.

What do you remember between sessions?

What do you forget?

You need to know what you're working with before you can improve it.

And also you need to know the limitations.

Most tools still have gaps in cross-session memory in what they retain versus discard, and also in how context window interact with the stored memory.

So by understanding the limitations, you will get significantly better results.

And for the more advanced users, I would encourage you to add specialized memory for your work context.

So some people maintain a running log.

Others create structured memory files.

Some people use dedicated memory tools or MCP servers.

What I want you to be is to be deliberate about what gets remembered.

Your agent does remember things on its own, but it doesn't always pick up the right things.

So a major decision, a change in priorities, or the end of a very long session might not be picked up properly how you would expect.