I build my LLM a Brain

2 points by Kevintbt ↗ HN
A glimpse about my app context engineering

Take a look :

https://x.com/TabetKevin/status/2048884876603203850

Have a nice one, feel free to comment, i want to so better

4 comments

[ 32.8 ms ] story [ 858 ms ] thread
All of these systems that try to solve "the memory problem" seem to fail to justify inserting either a layer of complexity with multiple moving pieces, or an outright blackbox. What is it that makes these systems worth the cost? What is it that they do that provide significantly more value than a structured directory of markdown files, a tuned grep search, and the model you are already using to synthesize the results? If you want to kick it up a notch, abstract the mechanism into a sub-agent to avoid context pollution. I have yet to find a memory system that clearly articulates how it is worth the overhead compared to the simple solution described.
Context engineering is where the real leverage is right now. Most people focus on model selection but the retrieval and memory layer around the model makes a bigger difference in practice. What's your approach to managing context window limits — chunking with overlap, or some kind of relevance scoring before injection?
As i said in the article, i have a filter for retrieval. I dont elaborate because i want to make it simple to read. You have the good structure, filtering, score relevance for every memories and indexes to facilitate the search ! You can check Supermemory infra its a bit how that works behind on chaaaaa.com