Two execution traces can look completely different even when nothing important changed.
Timestamps, random IDs, and event ordering create noise that makes real changes hard to spot.
Built TraceDiff: feed it two traces, get back only what actually changed.
Demo Link Below
I am just reading about agentic memory and its not ending 馃槶
I don't usually write technical articles, and I'm pretty weak at this stuff. I don't do it often, and because of that, whenever I write one, I keep thinking about how I should structure it correctly, and I have to invest a lot of time. Well well, anything I do, I have to spend a lot of time on, ahh.
So the writing stuff I鈥檓 trying out, tbh, is for better visibility (I know 99% of people are not going to read it still), and I will try to post only the stuff I actually know, to make full use of the blue tick. The end goal, after reading about these products and research papers, is to build an agentic memory, and I didn鈥檛 know a lot about agentic memory, so I鈥檓 spending time doing a thorough review of what鈥檚 available, how they address the problems related to agentic memory, and what problems still remain to be solved. After absorbing this content, I will talk about how I will build my own agentic memory. Happy if you all follow along
Lately I've been digging into agentic memory , and came across an interesting way it is being classified based on functionality:
Episodic memory - stores experiences and events.
Semantic memory - stores facts, concepts, and general knowledge.
Procedural memory - stores how to perform a task.
Reflective memory - derives lessons from past experiences and mistakes.
These aren't necessarily four distinct types of memory in every architecture. They're different aspects of how an agent stores, processes, and uses information, and they can work together to form a memory system.
What's interesting is that each aspect comes with its own set of challenges that researchers are actively trying to solve.



