tamaratran/fast-jev-compaction

Claude Code plugin that replaces the compaction summary with Jev decisions: every tool call and result is scored in one fast request, stale ones are dropped...

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 8 minutes ago
Added to GitGenius on September 19th, 2026
Created on September 17th, 2026
Open Issues & Pull Requests: 66 (+1)
GitHub issues: Enabled
Number of forks: 332
Total Stargazers: 5,941 (+14)
Total Subscribers: 13 (-1)

Repository Insights (GitGenius)

Median issue/PR response: 1.8 hours
Mean response time: 5.4 hours
90th percentile: 11.2 hours
Tracked items: 4

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 23
New in 7 days: 25
Closed in 7 days: 2
Avg open age: 1 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 25
Closed in 7 days: 2
Comments in 7 days: 6
Events in 7 days: 7

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.

Detailed Description

fast-jev-compaction is a Claude Code plugin that replaces context compaction with lossless message pruning based on relevance scoring.

The problem it solves is that traditional context compaction summarizes old conversation turns, which loses exact details like file paths, error messages, or constraints that may matter later. This tool takes a different approach: it never rewrites anything. Instead, it uses a language model to score each tool call and its result for relevance, then deletes only those marked as no longer needed while keeping everything else verbatim and in original order. The full conversation is shown to the scoring model, with tool results replaced by brief notes, so decisions are made with complete context.

The tool works by pairing each tool call with its result, pinning recent messages to preserve them, and fitting the conversation into token limits through staged truncation strategies. It sends the full conversation state to the scoring model with two questions per tool call: whether the call itself should stay and whether its result should be kept verbatim or truncated. Decisions are made against a configurable threshold, and messages that lose all content are removed while untouched messages are returned unchanged. The project is available both as an npm package and as a Claude Code plugin. Anyone adopting it should know that it requires careful configuration of token limits and thresholds, and that it will throw errors rather than silently degrade if the conversation cannot be fitted within constraints. It suits teams using Claude Code who need to preserve exact technical details across long conversations without losing information to summarization.

The project shows active maintenance with recent commits addressing core functionality. Development includes both the plugin implementation and the underlying library, with careful attention to token estimation and the mechanics of message reconstruction. The codebase handles edge cases like malformed responses and missing keys by throwing errors that let callers decide on fallback behavior.