Context filtering does not rewrite JSONL
The README distinguishes the model-visible surface from the persisted session file. This is an important recovery difference from replacing history with a new summary.
Inspect the supporting source ↗A Pi extension that prunes stale tool history verbatim and falls back to Pi summary compaction when needed.
Judges whether calls and outputs should survive in the context sent to the model.
Retains the original session file and records pruning decisions.
README and integration source reviewed at a fixed commit; not independently run or benchmarked by this site.
Reduce the context sent to a stock Pi model while preserving the session’s original log.
Material analysed:
The README distinguishes the model-visible surface from the persisted session file. This is an important recovery difference from replacing history with a new summary.
Inspect the supporting source ↗The ledger is merged only after a complete valid result; timeout, malformed answers or insufficient reduction leave Pi’s built-in summary path available.
Inspect the supporting source ↗Choose it for stock Pi when recoverable original history matters. Check branch behavior and actual recall instead of equating a smaller context with unchanged task quality.
Read actionsFor/decision branches in src/core/decide.ts and the README ledger description. Trace a pinned call, a keep-result answer and a keep-call-only answer, then compare the session log with the model-visible policy.