Community · E2 · artifact verified
Prune stale coding-agent tool history
A Pi extension uses Jev to decide which old tool calls and results still matter while keeping conversation text verbatim.
01 · Role in the system
What Jev does here
For each eligible tool call, Jev estimates whether the call and its result should remain in context. Code turns those probabilities into monotonic keep, truncate-result, or drop-call decisions, pins recent messages, records an append-only ledger, and falls back to Pi's built-in summary compaction when pruning is insufficient.
02 · Control boundary
Where Jev sits
Compact tool-history state to paired Noul judgments; code preserves order and applies reversible context filtering.
Code owns the loop, permissions, thresholds, validation, and side effects. Jev owns only the bounded judgments described above.
03 · Known limits
What this evidence does not prove
- Tool-call pairing depends on stable Pi identifiers and truncated results can lose attached images.
- Model judgments are not semantic proofs, and the extension does not create summaries or durable memory.
04 · Attribution
Public sources
This is a Community record: the project was published by a third-party community author.
- joelhooks ↗Community · github · public · checked 2026-09-18