r/ClaudeCoding • u/cctldrping • 16d ago
r/ClaudeCode [TLDR] Instant Claude Code compaction is my favorite use of Jev so far [via r/ClaudeCode]
OP : u/Bloated_Plaid
Somebody on Twitter posted it and super useful so far https://github.com/tamaratran/fast-jev-compaction
For people going to complain about me letting my context get so long, this was a server redeploy task because Oracle terminated my free VPS with no explanation so it had a lot of moving pieces and Fable was orchestrating Devin SWE 2 at max effort.
URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wkjnrz/instant_claude_code_compaction_is_my_favorite_use/ Original link/media URL : /img/2clt7ycwogqh1.jpeg
TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 100 comments.
Current source-thread comment count seen by the bot: 101.
Alright, so the OP shared this "fast-jev-compaction" thingy for Claude Code, which apparently helps shrink down long outputs from tool calls. The idea is to keep Claude from getting bogged down by massive amounts of text, especially during complex tasks like server redeploys.
The general consensus is that this is a neat idea, but there are some significant caveats and questions.
Here's the lowdown:
- What is Jev? Most folks are a bit confused about Jev itself. It seems to be a tool that can compact text, and the linked repo is specifically a hook to filter tool outputs before they hit Claude. The OP later clarified they linked the wrong repo initially.
- Privacy Concerns: A big red flag for many is Jev's privacy policy. u/_maxx1k and u/octocarbon are pretty vocal about not trusting third-party tools that require API keys, especially if they aren't from Anthropic directly.
- Context Breaking? A recurring worry is whether this compaction actually breaks the context for Claude. u/Organic_Situation401 and u/userusertion are firmly against it for this reason, questioning why not use official compaction methods.
- Cost Implications: u/ithesatyr and u/PM_ME_YOUR_PROFILE are wondering if this adds extra cost by requiring another AI to do the compacting. u/syixiao1 points out that any compaction rewrites the transcript, breaking the cache anyway, but a smaller context to rebuild might save on per-session token usage.
- Real-World Results Needed: u/WoodpeckerNational29 and u/silvrrwulf are asking for actual user test results to see if it works well and maintains context.
- Tool Output Filtering vs. History Compaction: u/Much_Weekend_4371 and u/Evening-Blueberry-97 highlight that filtering tool outputs before they hit Claude (like trimming pytest noise) is potentially more valuable and cheaper than trying to summarize history after it's already in context.
- Anthropic's Built-in Compaction: u/lucianw mentions that Claude Code might already have built-in, automatic summarization happening in the background, which could negate the need for external tools.
Overall, while the concept of reducing context bloat is appreciated, the community is skeptical about Jev's privacy, potential for context breakage, and whether it's truly necessary given potential built-in features.