正在加载视频...

视频加载失败

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 次观看 • 1 年前 •via X (Twitter)

27 条评论

Akshay 🚀 的头像
Akshay 🚀1 年前

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:

Akshay 🚀 的头像
Akshay 🚀1 年前

@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!

Avi Chawla 的头像
Avi Chawla1 年前

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.

Akshay 🚀 的头像
Akshay 🚀1 年前

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

Max Dziura 的头像
Max Dziura1 年前

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

Erez Vega Kadoch 的头像
Erez Vega Kadoch1 年前

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

LLM 的头像
LLM1 年前

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

Akshay 🚀 的头像
Akshay 🚀1 年前

What other use cases do you have in mind ?

Min Chon Chi 的头像
Min Chon Chi1 年前

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

Akshay 🚀 的头像
Akshay 🚀1 年前

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

Yuki He 的头像
Yuki He1 年前

real-time memory sharing? creators could finally breathe!

shyam🇮🇳 的头像
shyam🇮🇳1 年前

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

LLM 的头像
LLM1 年前

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

Dude 的头像
Dude1 年前

dude, thanks

Akshay 🚀 的头像
Akshay 🚀1 年前

@AlphaLebowski You're welcome! Cheers! :)

Agam Chaudhary 的头像
Agam Chaudhary1 年前

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.

Humble Billionaire 的头像
Humble Billionaire1 年前

Are we just rebuilding search engines?

Robert Youssef 的头像
Robert Youssef1 年前

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?

flying turtle 🐢 的头像
flying turtle 🐢1 年前

loved it bro. thanks

Akshay 🚀 的头像
Akshay 🚀1 年前

Glad you liked it! Cheers! :)

Xav 的头像
Xav1 年前

should try it with helix, we have a zep integration

Lucas Matuszewski 的头像
Lucas Matuszewski1 年前

@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!

Xiang Zhao 的头像
Xiang Zhao7 个月前

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.

Remembra Dev 的头像
Remembra Dev8 个月前

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.

AI/ACC 的头像
AI/ACC1 年前

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.

timely quantum / protocol architect 的头像
timely quantum / protocol architect1 年前

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

Prompt||GTFO 的头像
Prompt||GTFO1 年前

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

相关视频

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 次观看 • 6 个月前