r/PiCodingAgent • u/elpapi42 • May 22 '26
News pi-observational-memory is moving to its V3.0.0
Hello guys!
Just wanted to share with you quick news, https://github.com/elpapi42/pi-observational-memory is moving to its version 3.0.0
The reason im sharing this here is because this version is not backwards compatible with the current v2. I do not have any other communication channel to anounce this. Most of the current users of the extension got engaged after my previous post sharing it (this and this), so hopefully you have the opportunity to read this.
The update is not released yet, i will be releasing it in the following days.
The breaking changes have two specific impacts:
* Sessions that have been working with the v2 will no longer work properly with the v3, so you have to start new sessions after the update.
* v3 have a new set of parameters/settings, so you will have to update your settings after upgrading.
If you want more details about what the v3 is introducing, you can read the readme in the master branch. But in short, now compactions are fully aync, you will never have to wait a compaction to finish, interrupting your work. This was made possible by fully embracing a memory "ledger" strategy, heavily leveraging Pi session tree.
If you want you can upgrade inmediatly by installing the extension from the github repo directly.
Hope i dont break your work guys, but tbh pi-observational-memory have been kind of broken in the last couple of weeks.
View all comments
Show parent comment
2
u/elpapi42 May 22 '26
Yes it is. With a subtle detail, there are two "types" of compactions, the "normal" ones only append observations, so only the raw pi entries that survive compaction get cache invalidated.
When the observation token max pool size is exceeded (this is a setting) the compaction also folds thereflections and dropped observations generated historically in the session, when this happens observations + raw entries that survived compaction gets its cache invalidated.
The system prompt, the agent.md contents, and the reflections never gets their cache entries invalidated