Shah: Supermemory dynamically injects under 2,000 tokens via deterministic hooks
Dhravya Shah · ⚡️ OpenClaw's Memory Sucks and the fix is simple — Dhravya Shah, Supermemory · Mar 9, 2026 · at 10:13
Dhravya Shah details Supermemory's architecture for agent context management compared to traditional RAG or tool-driven memory search.
0:00 / 0:29exact quote · 29.2s
▶ Watch the full episode on YouTube → 720p mp4 · rendered on demand · StarZero watermark
“So we basically turned the tools based approach to hooks based approach that actually is dealing from the super memory graph, which keeps the content fresh. So it handles updates, et cetera. So now, you know, for every tool call or for every user message, a hook automatically will put Less than 2000 tokens worth of information dynamically. So the entire context will not have more than 2000 super memory tokens.”
quote is from the automated transcript, cleaned for reading: filler sounds and stutters are removed, nothing is rephrased. names can be misheard (the analysis reads context, assessments check outside sources). how →
More from Dhravya Shah
Shah: Claude Code avoids indexing because vendors profit from high token usage
“They could index the code and cursor does, but plot code does not. And I believe this is also because they are not incentivized to utilize less tokens by the end user, because they're just offsetting the cost of indexing, et cetera, to tokens and time that the…”
Shah: OpenClaw memory fails because LLMs frequently skip search tool calls
“The way OpenClaw has with QMD or with whatever memory plugin you use, it inherently relies on tools to search through these memory.md files that it prepares. So, you know, like, what did I decide about the API? Then agent will decide to search, and sometimes i…”
Shah: OpenClaw's 15-message replay fails prompt caching and costs 10x more
“The way OpenClaw does it is it essentially sends back the last 15 messages in the conversation and it essentially uses that back and forth. And I mean, the approach itself is not ideal because you will, like, you are not doing any, like, you're not utilizing a…”
Shah: Most vector databases become too slow or expensive at scale
“So, so, better databases, like, at that time, and even now, except a few, like, TurboPuffer and Chroma, Were not really scalable for the scale I was getting to where they were either getting too slow or too expensive to run.”