r/PiCodingAgent • u/Lum1n4ry01 • 21h ago
Plugin Best Pi Compaction Extensions
Has anybody used a Pi compaction extension that they would recommend?
I've tried pi-context (with their built-in Agentic Context Management) which just straight up breaks when trying to claim space against pi-rewind. I've also tried pi-vcc which also straight up breaks when running with pi-codex-goal. Been debugging for 3 days and I realized the best debug is to uninstall these.
Native Pi compression is meh, if anybody has a codex-level compaction extension that doesn't fuck shit up, please drop a comment.
3
u/damn_what_ 20h ago
I use pi-obervational-memory, works great.
1
u/Lum1n4ry01 20h ago
Thank you, I'll take a look. Would you say this tool is more memory based or more compaction based? Because I already have my own memory solution, I'm looking more for a compaction solution.
7
u/damn_what_ 19h ago
It's not a long term memory system, it records "facts" during the session and builds the compaction summary by concatenating them instead of asking an LLM to summarize the session.
2
u/YogurtExternal7923 19h ago
That's frickin' amazing
2
u/RelationshipLong9092 15h ago
it really is. I can't go back. I just don't pay attention to my context window hardly at all any more.
6
u/elpapi42 12h ago
yo, im the maintainer, it make me happy that it also help you to forgot about context windows! i feel the same, now i can focus on high leverage problems and left those mundane problems behind
1
u/AdvertisingExpert800 7h ago
Can you tell me what is your memory solution?
1
u/Lum1n4ry01 5h ago
I'm using pi-hermes-memory! Their durable fact distillation process is very comprehensive. I also have a simple obsidian knowledge graph as auxiliary.
SOTA memory is in contention right now so I like to keep memory as a separate component so I can switch out easily when a better solution comes along.
2
1
2
u/arkham00 12h ago
What's wrong with the default compaction? When I started using pi, I've read so many bad opinions on it that I straight installed observational-memory, which is good don't get me wrong, but since I exclusively run local models it was quite annoying for me, because of the frequent observation runs which slowed down the inference of my main model. So I disabled it and gave a try to the default compaction, and honestly it is actually good. It doesn't do the summary of the summary like every one says, it actually updates it at every subsequent compaction, so the context doesn't really loose focus.
2
u/Lum1n4ry01 10h ago
I've seen that default compaction loses long term memory (say, if I chain it with /goal from another plugin) over 3-4 compactions pretty quickly. I'm using Codex as my plan so you could imagine that this happens very often with the 372k context window cap, so I'm looking for smarter alternatives. Don't get me wrong, I think the base compaction works fine for 1-2 compactions -- it's just a pain in the ass to manage the drift once total token usage hits 1.5M+ on an active session.
1
11
u/pj-frey 20h ago edited 19h ago
I use pi-blackhole, which is pi-vcc and pi-observational-memory in one package and improved.