REPOSITORY ANALYSIS

pi-fast-jev-compaction

A Pi extension that prunes stale tool history verbatim and falls back to Pi summary compaction when needed.

E2 · source reviewedPublic material or source evidence was reviewed. A fixed-version source review requires checking a pinned revision; this is not a reproduction, performance endorsement, or safety guarantee.
Stars
11
Forks
2
License
MIT
Last commit
2026-09-18

What Jev does here

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.

What task does this project fit?

Reduce the context sent to a stock Pi model while preserving the session’s original log.

Material analysed:

From input to action

  1. The extension pairs tool activity and asks two keep Nouls per eligible call.
  2. Local policy maps them to keep, drop_result or drop_call.
  3. Append-only custom decisions rebuild a branch-specific ledger on resume, fork or tree navigation.

Implementation details that matter

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 ↗

Failure fallback remains available

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 ↗

When to choose it

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.

How to inspect it yourself

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.

Limits of this review

  • No Pi extension or model call was executed.
  • Version compatibility refers to the stock Pi version documented at this fixed revision.
Primary material used in this analysis