Workflow guide
Keep tool results verbatim instead of summarizing
Use Jev as a keep-or-drop judge for agent transcripts, following the fast-jev-compaction pattern.
Step 1
Pin the newest turns
The compaction library never touches the first message or the newest preserveRecentMessages turns. Copy that idea even if you do not use the plugin.
Step 2
Send the whole conversation as state
Replace bulky tool outputs with a one-line note such as character count, but keep tool names and inputs. Do not ask Jev to write a summary.
Step 3
One Noul per keep/drop decision
Ask whether this tool call still matters, and whether its full output should stay. Then delete or truncate in your code. That is what fast-jev-compaction does on GitHub.
Step 4
Require a TypeSafe key on the machine that calls Jev
The official endpoint is POST https://api.typesafe.ai/v1/systemone with a Bearer key. JEV Hub will not call it for you.
Related projects
- fast-jev-compaction — Claude Code plugin and npm library that asks Jev which tool calls to keep, instead of summarizing the transcript.
- jev-sentinel — Pi, Claude Code, and Codex CLI guard that asks Jev whether a tool call is on-task, risky, or injected before it runs.