Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

knowledge graphs are INSANELY good at giving agents human-like memory! today, we're building an MCP-powered memory layer that can be shared across all your AI apps like Cursor, Claude Desktop etc. it's built using a real-time knowledge graph. 100% open-source and self-hosted.

57,540 Aufrufe • vor 1 Jahr •via X (Twitter)

27 Kommentare

Profilbild von Akshay 🚀
Akshay 🚀vor 1 Jahr

tech stack: - @zep_ai 's Graphiti as a memory layer - @neo4j to store the knowledge graph - @Docker to self host the MCP server find all the code here:

Profilbild von Akshay 🚀
Akshay 🚀vor 1 Jahr

@neo4j @Docker If you found it insightful, reshare with your network. Find me → @akshay_pachaar ✔️ For more insights and tutorials on LLMs, AI Agents, and Machine Learning!

Profilbild von Avi Chawla
Avi Chawlavor 1 Jahr

solving a really good problem here using knowledge graphs and memory. I think most people use AI apps in silos and there's no simple way to automatically connect them via a shared memory.

Profilbild von Akshay 🚀
Akshay 🚀vor 1 Jahr

Absolutely, everyone can benefit from this. Shared memory has a tons of use cases.

Profilbild von Max Dziura
Max Dziuravor 1 Jahr

Knowledge graphs for AI memory; brilliant. Maybe my to-do list will finally remember itself.

Profilbild von Erez Vega Kadoch
Erez Vega Kadochvor 1 Jahr

What about latency? When your graph has multiple nodes and relationships, it takes more time to retrieve high quality result and rerank it. How do you deal with that? That’s my biggest issue with graphs atm

Profilbild von LLM
LLMvor 1 Jahr

This is a huge step forward—shared AI memory is game-changing.

Profilbild von Akshay 🚀
Akshay 🚀vor 1 Jahr

What other use cases do you have in mind ?

Profilbild von Min Chon Chi
Min Chon Chivor 1 Jahr

The open-source aspect is a big plus, but I wonder about the scalability of a self-hosted solution for many users.

Profilbild von Akshay 🚀
Akshay 🚀vor 1 Jahr

Scalability is not an issue, you can always deploy this container in a any scalable cluster.

Profilbild von Yuki He
Yuki Hevor 1 Jahr

real-time memory sharing? creators could finally breathe!

Profilbild von shyam🇮🇳
shyam🇮🇳vor 1 Jahr

Could you suggest best RAG solution that supports AWS Bedrock ?? Thanks in advance!!!

Profilbild von LLM
LLMvor 1 Jahr

This looks amazing! Can’t wait to see AI apps with shared memory.

Profilbild von Dude
Dudevor 1 Jahr

dude, thanks

Profilbild von Akshay 🚀
Akshay 🚀vor 1 Jahr

@AlphaLebowski You're welcome! Cheers! :)

Profilbild von Agam Chaudhary
Agam Chaudharyvor 1 Jahr

A shared memory layer changes the game. Agents that can retain and connect experiences across apps start to feel less like tools and more like collaborators. It opens up the question of what new kinds of workflows become possible when memory is no longer siloed.

Profilbild von Humble Billionaire
Humble Billionairevor 1 Jahr

Are we just rebuilding search engines?

Profilbild von Robert Youssef
Robert Youssefvor 1 Jahr

this is a solid approach to breaking down silos. shared memory really can change how we use ai apps together. any plans for more integrations down the line?

Profilbild von flying turtle 🐢
flying turtle 🐢vor 1 Jahr

loved it bro. thanks

Profilbild von Akshay 🚀
Akshay 🚀vor 1 Jahr

Glad you liked it! Cheers! :)

Profilbild von Xav
Xavvor 1 Jahr

should try it with helix, we have a zep integration

Profilbild von Lucas Matuszewski
Lucas Matuszewskivor 1 Jahr

@akshay_pachaar When would you use Graphiti vs MindsDB for real-time distributed data like social media posts and interactions or crypto / blockchain transactions and trends? BTW, your content is amazing, thank you!

Profilbild von Xiang Zhao
Xiang Zhaovor 7 Monaten

Knowledge graphs are great for this! LATRACE takes it further—event-centric where time is the anchor, state changes are first-class. Text/video/audio in same pipeline → knowledge graph. SOTA on temporal reasoning.

Profilbild von Remembra Dev
Remembra Devvor 8 Monaten

Knowledge graphs + semantic memory is the move. We built similar at Remembra — bi-temporal versioning so you can query what the agent knew at any point in time. Critical for debugging multi-agent workflows. Also MCP-native, self-hosted. Different architecture but same goal: agents that actually remember.

Profilbild von AI/ACC
AI/ACCvor 1 Jahr

Knowledge graphs drastically reduce AI agent hallucinations. True reliability demands structured context and explicit, traceable verification checks at every workflow step, not just final output.

Profilbild von timely quantum / protocol architect
timely quantum / protocol architectvor 1 Jahr

knowledge graphs for AI are what spacetime is for consciousness, a living network of stored relationships, updating itself in real time. #MST #MultiSimulationThesis

Profilbild von Prompt||GTFO
Prompt||GTFOvor 1 Jahr

Come show us live on @promptorgtfo? CC: @gadievron

Ähnliche Videos

RAG might already be becoming obsolete. A month ago, Andrej Karpathy dropped a simple GitHub gist called “LLM Wiki.” Now the comments section looks like the birth of an entirely new AI category. 5000+ stars later, developers are rapidly building: • persistent AI memory systems • self-maintaining knowledge bases • multi-agent research environments • contradiction detection engines • AI-native company operating systems • local-first memory architectures • graph-based reasoning layers • evolving second brains And the craziest part? Most of them were built in DAYS. Because the core idea is insanely powerful: Instead of AI repeatedly retrieving raw chunks like traditional RAG… …the model continuously maintains a living knowledge system. Not temporary context. Persistent synthesis. The shift sounds subtle until you realize what it changes: RAG: retrieve → answer → forget LLM Wiki: ingest → synthesize → evolve That one architectural difference is causing an explosion of experimentation right now. People are already building: • agent memory operating systems • AI-maintained engineering documentation • self-healing knowledge graphs • persistent research environments • conversational memory architectures • contradiction-aware wikis • context compression engines • machine-readable company systems The comments section alone feels like watching an ecosystem form in real time. One developer built deterministic contradiction detection using sheaf cohomology Another built “sleep consolidation” for AI memory systems inspired by human memory formation Another created persistent multi-agent vault conversations Another turned entire repositories into continuously maintained AI wikis Another built local-first memory systems with audit trails, provenance, graph exports, and MCP integration This is the important part: Karpathy didn’t launch a product. He introduced a pattern. And patterns are what create ecosystems. The same way: • transformers created modern AI • RAG created AI retrieval startups • agents created orchestration frameworks LLM Wikis may create persistent AI memory infrastructure. That’s why this moment feels different. For years, AI systems have been stateless. Now developers are trying to build systems that actually accumulate understanding over time. And once knowledge compounds instead of resetting… …the entire interface layer of AI changes. (Link in comments)

Suryansh Tiwari

143,793 Aufrufe • vor 6 Monaten