fast-jev-compaction vs SoL-Pi
Claude Code plugin and npm library that replaces compaction summaries with Jev decisions: every tool call and result is scored, stale ones dropped or truncated, everything kept stays verbatim. — versus — NVIDIA's Pi extension with four auto-research-discovered efficiency mechanisms - action fusion, observation packing, evidence-preserving log reduction, online context compaction - all opt-in.
sol-pi's ObservationPack and evidence-preserving reducer solve the same replay problem inside Pi with quotation checks; fast-jev-compaction solves it in Claude Code by scoring each call with Jev.
| fast-jev-compaction | SoL-Pi | |
|---|---|---|
| Stars | 4.2k | 2.4k |
| Forks | 221 | 187 |
| Language | TypeScript | TypeScript |
| License | MIT | MIT |
| Last activity | yesterday | today |
| Topics | coding, agents | coding, agents |
| Curated connections | 5 | 7 |
fast-jev-compaction — the curator's take
The sharpest idea in agent context management right now: never rewrite, only delete. A summary can silently lose the exact error, path or constraint you need twenty turns later; this scores each tool call and result with two noul questions against the whole conversation and then removes rather than paraphrases, so user and assistant text survives byte-for-byte. Fitting the state into 25k tokens is staged and documented, and it throws instead of guessing when history won't fit. Use it when losing a literal detail is the failure you fear. Don't use it if your bloat is prose rather than tool output - text is never shortened in the output - and note the honest limitation in its own README: a keep probability is not a proof that a result is safe to delete. Needs a hosted TypeSafe key on every compaction.
SoL-Pi — the curator's take
Install SoL-Pi if you run Pi as your coding agent and want fewer turns and less context replay without the agent skipping work: Action Fusion runs an edit's validation command in the same tool call, ObservationPack turns repeated big tool results into paged handles, the Reducer only compacts a log when every retained quote still matches the archive. It is an extension over unmodified Pi 0.85.1 - no patches, everything disabled until you write sol-pi.json. Not for Claude Code/Codex users (it uses Pi's extension APIs); headroom, rtk and token-optimizer are the harness-agnostic ways to get the same effect. The paper is the interesting part: the mechanisms were found by scaled auto-research loops over the harness itself, which is autoresearch/evo pointed at agent efficiency.