I have a question regarding the memory simplification. I bought the stack and trying to understand where the simplification took place. Now you are using memory , memory-weekly and memory-index in the system. Is this the simplification from a "bigger memory system"?
Yes, exactly. The 3-tier system (memory, memory-weekly, memory-index) is the result of simplifying what was a much messier setup.
Originally Wiz had a sprawling memory - multiple overlapping files, no clear ownership of what goes where, no compression. The agent would read everything at session start and burn through context window on stale data. Stuff that mattered 2 weeks ago was sitting right next to what happened yesterday, same priority.
The simplification was: give each file a clear time horizon. memory.md = last 2-3 days (detailed). memory-weekly.md = 7-10 days (compressed). memory-index.md = permanent but keywords only (people, projects, locations - just enough to know where to look). Then rollover.py moves things down the chain automatically.
The "bigger memory system" wasn't one deliberate design -it was organic growth that turned into a mess. The 3-tier version is what survived the cleanup.
Impressive execution on the self extension pattern. The gap between having an agent that complains about missing capabilities vs one that just builds them is huge. What surprised me most was the error registry approach, most people would try some kind of reinforcement loop but explicit logging and scheduled maintainance is way more reliable. Watching your agent draft 133 social comments while you sleep feels like the future arriving quietly.
Reading through many of your articles. Great ideas and insights. Thanks for sharing
Thanks!
Great stuff on this one Pawel. And i love the art for the hero image too. Hopefully we see more adoption of this type of pattern.
Absolutley great insights!
I have a question regarding the memory simplification. I bought the stack and trying to understand where the simplification took place. Now you are using memory , memory-weekly and memory-index in the system. Is this the simplification from a "bigger memory system"?
Yes, exactly. The 3-tier system (memory, memory-weekly, memory-index) is the result of simplifying what was a much messier setup.
Originally Wiz had a sprawling memory - multiple overlapping files, no clear ownership of what goes where, no compression. The agent would read everything at session start and burn through context window on stale data. Stuff that mattered 2 weeks ago was sitting right next to what happened yesterday, same priority.
The simplification was: give each file a clear time horizon. memory.md = last 2-3 days (detailed). memory-weekly.md = 7-10 days (compressed). memory-index.md = permanent but keywords only (people, projects, locations - just enough to know where to look). Then rollover.py moves things down the chain automatically.
The "bigger memory system" wasn't one deliberate design -it was organic growth that turned into a mess. The 3-tier version is what survived the cleanup.
Nice follow up explanation! love to see authors who care enough to keep the deep dive going in the comments.
Impressive execution on the self extension pattern. The gap between having an agent that complains about missing capabilities vs one that just builds them is huge. What surprised me most was the error registry approach, most people would try some kind of reinforcement loop but explicit logging and scheduled maintainance is way more reliable. Watching your agent draft 133 social comments while you sleep feels like the future arriving quietly.
+1!
Thanks!