Daniel Chalef (@danielchalef) 's Twitter Profile
Daniel Chalef

@danielchalef

Working on Zep: Long-term memory for enterprise AI apps. @zep_ai

ID: 7051032

linkhttp://www.getzep.com calendar_today24-06-2007 13:53:34

1,1K Tweet

1,1K Followers

1,1K Following

Avi Chawla (@_avichawla) 's Twitter Profile Photo

2️⃣ Graphiti MCP server Agents forget everything after each task. Graphiti MCP server lets Agents build and query temporally-aware knowledge graphs, which act as an Agent's memory! Check thisπŸ‘‡

Thomas Roccia 🀘 (@fr0gger_) 's Twitter Profile Photo

πŸ€“ RAG are powerful. They allow you to search your own knowledge base and extend your AI system with your own data. A RAG injects relevant context into the context window tailored to your domain. But most RAG setups are static. They require manual update, it is slow and

Avi Chawla (@_avichawla) 's Twitter Profile Photo

Today, we'll add a common memory layer to Claude Desktop and Cursor so users can cross-operate without losing context. Our tech stack: - Zep AI Graphiti MCP as a memory layer for AI Agents. - Cursor and Claude as the MCP hosts. Let's begin!

Daniel Chalef (@danielchalef) 's Twitter Profile Photo

Super honored to be voted one of their best speakers at AI Engineer 2025! πŸŽ‰ Thanks to swyx and team for organizing such a fantastic event. πŸ’™ If you missed this year, def make a plan to attend next year’s event!

Akshay πŸš€ (@akshay_pachaar) 's Twitter Profile Photo

Build an MCP-powered shared memory for all your AI apps! Using real-time knowledge graphs! 🧠 (switch apps, not the context)

Daniel Chalef (@danielchalef) 's Twitter Profile Photo

The Daily Dose of Data Science guys are awesome! You should subscribe! (and I love that they build stuff with Zep AI and Graphiti ❀️)

Alexander Belanger (@b39241belanger) 's Twitter Profile Photo

the only primitives that should be shared across most AI agents: durable execution, memory, and observability. the argument is simple: the best AI apps aren't using frameworks. don't let artificial constraints or abstractions built by someone else impact your product direction.

the only primitives that should be shared across most AI agents: durable execution, memory, and observability. 

the argument is simple: the best AI apps aren't using frameworks. don't let artificial constraints or abstractions built by someone else impact your product direction.
Akshay πŸš€ (@akshay_pachaar) 's Twitter Profile Photo

1️⃣ Graphiti MCP server Agents forget everything after each task. Graphiti MCP server lets Agents build and query temporally-aware knowledge graphs, which act as an Agent's memory! Check thisπŸ‘‡

Zep AI (@zep_ai) 's Twitter Profile Photo

Context engineering is replacing "prompt engineering" β€” and it's about time πŸš€ ➑️ The industry is shifting from prompt hacking to building production systems that actually work. 🎯 Context engineering = dynamic systems that feed LLMs exactly what they need, when they need it πŸ“ˆ

Context engineering is replacing "prompt engineering" β€” and it's about time πŸš€

➑️ The industry is shifting from prompt hacking to building production systems that actually work.

🎯 Context engineering = dynamic systems that feed LLMs exactly what they need, when they need it
πŸ“ˆ
Zep AI (@zep_ai) 's Twitter Profile Photo

Graphiti now supports falkordb ! Build temporally-aware #GraphRAG using FalkorDB's super-fast database! Thanks to the FalkorDB team for their awesome work here!

Akshay πŸš€ (@akshay_pachaar) 's Twitter Profile Photo

CrewAI Zep AI Comet Here's an overview of the system we're building! - User sends a query - Assistant runs web search via MCP - Query + results go to Memory Manager - Memory Manager stores context in Graphiti - Response agent crafts the final answer