Prunes old tool calls and outputs for Claude Code while retaining surviving text verbatim.
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.
Separately judges whether a tool call and its full output are still needed; code keeps, truncates or drops them.
WHY IT HELPS
Avoids rewriting paths, commands and errors into a new summary.
SOURCE NOTE
Requests are split to fit budgets, rather than always using one call. Pruning can remove useful context; the animation is not a live API benchmark. README and integration source reviewed at a fixed commit; not independently run or benchmarked by this site.
Prune Claude Code tool history while keeping retained evidence verbatim.
Material analysed:
From input to action
Code pairs tool calls with results and pins protected messages.
Jev answers separate keep-call and keep-result Nouls for eligible pairs.
Local thresholds keep both, truncate the result head, or drop the pair; failures retain the built-in fallback.
Implementation details that matter
Verbatim retention is narrower than lossless context
User/assistant text is retained, but tool results may be truncated or removed. The state sent to Jev abridges tool output, so its decision does not necessarily inspect every original byte.
The pinned README describes estimated token fitting and repeated shared state. These are this plugin’s budgets, not a universal current TypeSafe account quota.
Useful where exact tool output matters more than a summary. Before trusting compaction, test later recall of paths, errors and constraints against both compacted and original histories.
How to inspect it yourself
Read README’s three decisions and client.ts transport seam. Compare keepResult above threshold with keepCall-only and neither; check that each call/result pair stays structurally consistent in the documented policy.
Limits of this review
No Claude Code hooks were installed or executed.
A lower payload is not evidence of unchanged task success or billing savings.