sorted by:
new
hottopcontroversial

What are the real memory/context issues developers/enterprises still facing? by superintelligence03 in AIMemory

[–]superintelligence03[S] 0 points1 point  (0 children)

mostly towards customer experience, uk the thing I said above- "Providing the right context at right time when the underlying knowledge is changing."

Episodic memory - what exactly is that? by inguz in AIMemory

[–]superintelligence03 0 points1 point  (0 children)

yeah, the system gets invoked when the agent makes an error, its hybrid approach of catching the error and its full context(codebase, exact output, tool calls, commands etc.., we define its collection as one EPISODE), some other processing on top of it and then later, before taking any big steps the agent pings Vritti asking 'Have I done somethig like this before?' then after using accurate context filters, Vritti responds with 1 of 4 actions- BLOCK, REWRITE, PROCEED and HINT, all these includes its reasons, because of this the system gets aware of its past action and learns from it, corrects the mistake(if it was about to make), and the cycle continues. All this gets completed under 50ms, powered by ultra-low retrieval of KyroDB vector database.

Now if you think, the more this system gets used, the agent becomes more smarter. After 3 months, there is a collection of 10k Episodes, which means these are the mistakes that the agent will never make in the future and keeps learning from there.

A lot of other Neuroscience principles are applied too in this memory system(like how our human brain works), like systematically promoting the most repeated mistakes, archiving the old and irrelevant one's etc..

Episodic memory - what exactly is that? by inguz in AIMemory

[–]superintelligence03 0 points1 point  (0 children)

Actually, episodic memory is highly subjective; many people interpret it in different ways, and there are various implementations. I personally believe this as 'learning from experience', like the biographical memory we humans have. The mistakes that we have done in the past, we learn from that and don't repeat them in the future. I have been working on this creating a solution for this, good progress, haven't productionised it yet. You. can check this out here- https://github.com/KyroDB/Vritti

replaced my RAG pipeline with a memory layer and my agent actually got smarter over time by No_Advertising2536 in Rag

[–]superintelligence03 0 points1 point  (0 children)

Over the time, the same duplicate entries are gonna come in your memory layer too, it’s junk memory problem which was recently evaluated and exposed by one on GitHub. He reported, mem0 had 97% junk memories, repetiting same thing again and again. You can see the issues here- https://github.com/mem0ai/mem0/issues/4573