yottayoshida/lossless-compaction
User repository on GitHub
Lossless compaction for Claude Code: move old context to local files and recall it exactly when needed.
- Forks
- 1
- Last pushed
- Updated Oct 2026
Repo stats from the GitHub API, cached Oct 2026.
CommunityJev Tools & CLIs
Lossless Compaction
Claude Code plugin that compacts conversations by moving old tool results to local files instead of summarizing them, leaving a ticket line in their place. When the agent needs something back, Jev can choose among the moved-out items in words for a `find`, while `recall` restores any item exactly by id.
- Stars
- 0
- Language
- TypeScript
- License
- APACHE-2.0
- Published by
- Community
- Last verified
- Oct 2026
About this project
Claude Code's /compact asks a model for a summary: tens of seconds, a request the size of the conversation, and the summary in place of what was said. This plugin moves old tool results out instead, leaving a line in their place. That takes a fraction of a second and calls no model, and what you and the agent said, Claude Code's attachments included, is stored word for word. Where that is not enough, the oldest messages are stored and listed in their place. What left is out of sight until recalled (limits).
Quoted from the project's README. Read the full README.
Works forJev for Routing
Used inJev for Software & DevTools
- Languages
- TypeScript
- Platforms
- CLI
- Capabilities
- Open sourceRuns locally
Highlights
- Records a compaction in 61 ms with no model call, against 15-27 s for the built-in summary in its own benchmark.
- Its six-conversation benchmark answered 102 of 108 questions correctly against 96 built-in, at $0.65 vs $2.17 for the first run.
- Results are stored as plain files named by SHA-256; recall restores a result word for word.
- Installs with /plugin install lossless-compaction on Claude Code 2.1.287 or later.
Watch out
Dual-licensed under Apache-2.0 or MIT. The word-based find sends conversation excerpts to your Jev provider once a key is set, and stored tool results remain on disk as plain files.
Questions about this entry
Short answers drawn from the linked project or page.
No. It moves old tool results to local files and leaves a ticket line in their place, so nothing is rewritten; a summary only runs if Claude Code's own compaction still triggers.
No. Recall by ticket id works without any key; only the word-based find, which asks Jev to choose among moved-out items, needs a Jev API key.
The plugin calls no model: its own count for one recorded compaction is 61 ms, against 15 to 27 seconds for the built-in summary in its six-conversation benchmark. That is what makes an instruction-free /compact instant.
Each result is written to a plain file named by its SHA-256 and read back before a ticket line replaces it. Results stay on disk as plain files while a conversation names them, with no size limit, and a secret inside a tool result is stored verbatim among them.
Once a key is set, find sends excerpts of the conversation to your Jev provider from every repository, unless you deny it. Recall by ticket id sends nothing to a provider and works without any key.
Claude Code 2.1.287 or later, checked on macOS, with other systems covered in the limits document. Install with /plugin install lossless-compaction --marketplace yottayoshida/lossless-compaction, then /lossless-status reports the version and settings.
Dual-licensed under the Apache License 2.0 or the MIT license, at your option. It shares no code with fast-jev-compaction, the project it credits as its idea, and it is not affiliated with TypeSafe AI or Anthropic.
Reactions & coverage
Posts, threads, and videos about this entry from around the web.
X: The compaction plugin, in Chinese
X: The compaction plugin, in Spanish
YouTube: Ray Amjad puts Jev inside an agentic coding loop and looks at what it costs to run.
YouTube: RoboNuggets puts Jev to work inside Claude Code.
More Jev resources like this
39.8kGitHub stars
A teams-first multi-agent orchestration plugin for Claude Code with opt-in Jev hooks for sub-millisecond judgment points, decision caching and per-point egress controls. TypeScript, MIT, with a staged team pipeline and tmux CLI workers.
Jev Tools & CLIs#community#claude-code#orchestration
13GitHub stars
Claude Code plugin and CLI that runs Claude Code on Opus 5.5 and has Jev re-decide the reasoning effort when a prompt arrives and after every tool batch, sending each change as a per-message effort statement inside one unbroken prompt cache.
Jev Tools & CLIs#community#claude-code#routing
Community
WXK-AI/jev-opusTypeScript
WXK-AI/jev-opusTypeScript11GitHub stars
Fuzzy linter hook for Claude Code and Codex: after the agent edits a file, it sends the added code to Jev, which answers Noul checks against team rule packs in about 0.3 seconds, letting the agent fix violations before code review.
Jev Tools & CLIs#community#linter#claude-code
Community
ckorhonen/jev-lintHTML
ckorhonen/jev-lintHTML0GitHub stars
A CLI, Claude Code plugin and Pi extension that pick a model per task from one Jev call: a Choice over candidates asked in both orders plus a complexity Score that sets a minimum tier, with quota-aware filtering and fallback.
Jev Tools & CLIs#community#routing#claude-code
Community
Ruivalim/decision-routerTypeScript
Ruivalim/decision-routerTypeScript20.4kGitHub stars
Rust coding-agent harness (MIT, ~20k stars) whose crates/jcode-base/src/jev.rs is a typed TypeSafe Jev decision transport, used for memory pruning (memory_jev.rs), browser navigation (browser_jev.rs), and voice routing (voice_intent.rs) with separate provider selectors per purpose.
Jev Tools & CLIs#community#rust#coding-agent
Community
1jehuang/jcodeRust
1jehuang/jcodeRust634GitHub stars
A CLI browser automation tool with optional Jev semantic mode: Surf observes, Jev selects the next action, Surf validates and acts, Jev checks the goal.
Jev Tools & CLIs#community#browser#cli
Community
nicobailon/surf-cliTypeScript
nicobailon/surf-cliTypeScriptFrom the Jev guides
Original write-ups on what this entry is for.
The request shape barely changes across surfaces; the surrounding contract does. When to call the API directly and when a gateway, a Worker binding, or a router entry earns its extra hop.
Jev Tools & CLIs#gateway#vercel#cloudflare
Read article
Taking a decision checkpoint out of Python: what the GGUF and browser WebGPU exports preserve, what they change, and the parity evidence the model cards publish.
Jev Tools & CLIs#open-models#local#onnx
Read article
Jev labels a record that already exists. Code moves, flags, or holds it. How the document, mail, and transfer tools keep the action out of the model.
Jev Tools & CLIs#classification#email#security
Read article
From the Jev community
Posts from builders shipping with Jev right now.