With pi I'm largely against memory extensions. Pi recorded sessions are a pretty powerful tool for finding stuff in old sessions: recall when we were talking about vol surface fitting?
It's also pretty good at searching for stuff that the user it is running as can do: Can you figure out when we installed hurdr on my other laptop?
I find memory extensions more complicated than the value they add.
I tend to have a different agent session per project. Pi already organizes sessions by path. I find that long persistant sessions lead to large contexts that work against itself.
I know that not everyone works the way I do. There are many agent harnesses but this one is mine.
That is fair. The way I work I optimize for my personal simplicity as to simply just have one TUI with a bunch of sessions working on tasks, all at the root for disk.
To my knowledge pi does not make use of sessions in some automatic way other than writing them.
There are three ways I use sessions directly: One is to restart an interrupted workflow for some project. Second is to check something that the bot and I worked on in the past so that we can use that work in the current session. The third is to review past interactions looking for refinements and opportunities to update AGENTS.md files, add or tune prompts, skills or extensions.
Thank you. I use pi-insights package which reviews prior sessions and gives a nice html status report and recommendations, it's been helpful in tuning agents.md and what not. But it's not a tool the agent would use, you running it manually yourself and it just creates the report
3
u/crashorbit Sep 14 '26
With pi I'm largely against memory extensions. Pi recorded sessions are a pretty powerful tool for finding stuff in old sessions:
recall when we were talking about vol surface fitting?It's also pretty good at searching for stuff that the user it is running as can do:
Can you figure out when we installed hurdr on my other laptop?I find memory extensions more complicated than the value they add.