Context compression doesn't have to "rewrite history": this

@vintcessun 恒星sun · Sep 19, 2026 · case #008601 · listed via Jev Hub

Still from the clip posted with this case; watch it in the original post on X.

Builder wrote a Claude Code plugin that uses Jev to judge each tool call and value for retention, deleting stale calls and truncating low-value results.

The original post, translated

Context compression doesn't have to "rewrite history": this Claude Code plugin instead judges tool calls one by one and whether they are worth keeping. https:// github.com/tamaratran/fas t-jev-compaction … It uses the full conversation as judgment context, only deletes expired calls, truncates low-value results, and keeps the remaining content in its original text. It is better suited than summarization for preserving errors, paths, and constraints; when compression is insufficient or judgment fails, it falls back to the built-in summary.

Show the original post in its source language ▾

上下文压缩不一定要“重写历史”：这个 Claude Code 插件改为逐个判断工具调用和值不值得保留。 https:// github.com/tamaratran/fas t-jev-compaction … 它把完整对话作为判断背景，只删过期调用、截断低价值结果，留下的内容保持原文。比摘要更适合保留报错、路径和约束；压缩不足或判断失败时再回退内置摘要。

The post above is a machine translation from zh; the untranslated text is in the fold-out.

Engagement when collected

Likes0

Bookmarks0

Reposts0

Replies0

Quotes0

Numbers are a snapshot taken from X when the case was added to the library (schema v1, collected 2026-09-19); they will not match today.

Where this case fits

Filed under coding & developer tools. In the pattern Jev is built for, the model answers a bounded question per step — and ordinary code acts on the answer, because the answer is already a value rather than a paragraph. Other posts in the same family are on the coding & developer tools page.

🛠️ Coding & developer tools