jev-compactor

Design and tune synthetic coding-agent sessions to evaluate Jev context-window compaction.

465|41|Updated Aug 4, 2026
One-click install
npx skills add https://github.com/autonomous-ai/openharness --skill jev-compactor-autonomous-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jev-compactor
Source: https://github.com/autonomous-ai/openharness/tree/main/store/agents/jev-compactor/skills/compactor
Command: npx skills add https://github.com/autonomous-ai/openharness --skill jev-compactor-autonomous-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Tuning an LLM context-compaction strategy is hard to evaluate without a controlled testbed. This Skill lets you design synthetic coding-agent sessions with known ground truth, run Jev's keep/trim/drop compaction over them, and measure needle recall versus token reduction so you can find settings that hold recall while cutting the window aggressively. ## Core Features & Use Cases - Synthetic session design: Write task vocabularies in session.json and validate them with check.mjs, controlling distraction, target, trimTo, budget, noise, focus, and taskEvery knobs. - Ground-truth measurement: Every tool result is secretly labeled detail needle, gist needle, or junk, so verdict.json reports true needle recall, junk removed, and reduction against a summarize-instead baseline. - Real transcript analysis: Point source at a Claude Code .jsonl transcript to get an offline compaction plan with keep/trim/drop counts, token reduction, cost, and timing, using the mock judge when no Jev API key exists. - Use Case: Start at distraction 0.1, raise it in steps of 0.2, find where recall crosses your target, then adjust target, budget, or trimTo one at a time and report which fix held recall at the largest reduction. ## Quick Start Ask the agent to design a Jev Compactor session with custom task vocabularies, run check.mjs, and report the distraction level where needle recall drops below target along with the settings that fix it.

Frequently Asked Questions about jev-compactor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I tune context window compaction settings?

Start with distraction at 0.1, run a few compactions, then raise distraction in steps of 0.2 while watching needle recall in .harness/verdict.json. At the point recall crosses your target, adjust one knob at a time such as target, budget, or trimTo and report which change helped and what it cost in reduction.

How do I analyze a Claude Code transcript for compaction?

Copy the session .jsonl file from ~/.claude/projects/<project folder>/ into the workspace as my-session.jsonl and set "source": "my-session.jsonl" in session.json. The pane reports tokens before and after, keep/trim/drop counts, calls, time, and cost without exposing the transcript contents.

What is needle recall in context compaction?

Needle recall is the share of needed tokens that survive compaction. Read and Edit results for the current task are detail needles that should be kept, Grep, Bash, and WebFetch results are gist needles that should be trimmed to about 300 tokens, and everything else should be dropped.

Does Jev compaction work without an API key?

Yes. With no Jev key in the environment or credentials file, an offline mock judge runs and nothing leaves the machine. With a key, the task message, recent messages, and roughly 300-character heads of tool results go to the Jev API, and the report states which one ran.

Why does compaction recall drop at high distraction?

Junk that borrows the current task's vocabulary gets kept, so the window stays above target and the pressure pass trims the keeps Jev was least sure about, some of which are real needles. Sharper, non-overlapping task vocabularies reduce this confusion.