fast-jev-compaction 用 Jev 决定 agent 保留哪些上下文
社区插件用 Jev 判断哪些工具调用与结果该留，实验里通过率追平参考方案但漏掉关键证据。
After Jev went viral, does context still matter? Jev let me rethinking a basic assumption: does an agent need the entire conversation at every step? The official docs warn that irrelevant content reduces Jev 1.13’s accuracy. The community plugin fast-jev-compaction uses Jev to decide which tool calls and results to retain. Code deletes or truncates them; user and assistant text stays unchanged in the output. In a small September 18 experiment from a separate project, Jev matched the reference approach’s pass rate. But its selected evidence omitted a 20-minute reservation duration. The original record was still available; the agent never retrieved it. Keeping a complete history and reading it on every call can be separate design choices. Once relevance judgments become cheap enough, constructing context can become part of the model’s ongoing decision-making. Each piece of information should be reassessed against the task at hand.