Top Repos· Jev-Based· Harness· Last updated

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 or truncated, everything kept stays verbatim.”

Jev-Based rank #2In Harness #2

TL;DR

tamaratran/fast-jev-compaction showed up as Jev / System One related work: Claude Code plugin that asks Jev keep / drop / truncate on every tool call so compaction never rewrites kept text.

The author describes it as: “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 or truncated, everything kept stays verbatim.” That is their claim, not a bench this site ran.

Who it’s for

What’s inside

Top-level entries on GitHub at generation time: .claude-plugin, .gitignore, LICENSE, README.md, demo, examples, hooks, package-lock.json, package.json, src, tests, tsconfig.hooks.json, tsconfig.json, types. Read those before you trust a one-line install.

How to use

  1. Clone and follow the author’s TypeScript toolchain. Do not invent a package name.
git clone https://github.com/tamaratran/fast-jev-compaction.git
cd fast-jev-compaction
  1. If the project calls hosted Jev, you still need a TypeSafe console key or a documented gateway.
  2. Send a complete state and typed questions. Code owns control flow after the probabilities.

Hosted Jev still looks like a function call — wrapper or not:

{
  model: "jev-1.13.0",
  state: { source: "tamaratran/fast-jev-compaction", brief: "..." },
  questions: {
    gate: { type: "noul", instructions: "Should we act on this state?" },
    route: { type: "choice", instructions: "Pick one next system.", criteria: ["code", "review", "human"] },
  },
}

Try this

Put Jev on one real brief

Wire tamaratran/fast-jev-compaction so one real state (ticket, diff, or utterance) becomes a Choice plus a Noul. Do not ask Jev to write the user-facing reply.

Schema-safe ≠ correct

On a case tamaratran/fast-jev-compaction gets wrong, write down the schema-legal answer it returned and the human label. Do not “fix” it by asking Jev to generate an explanation.

FAQ

Does this replace the TypeSafe SDK?

Only if the author implemented a full client. Most harnesses still call the vendor SDK or raw HTTP.

Are the star chips live?

Star, fork, and watcher chips refresh from the public GitHub API via a scheduled job. The prose on this page is editorial.

Sources

Public repository metadata and TypeSafe documentation. No private claims.