Skip to content
JevDirectory.org
CommunityTools & Integrations10 starsVerified 2026-09-22

pi-fast-jev-compaction

A Pi extension that keeps conversation text verbatim while pruning stale tool history with Jev keep-or-drop decisions, falling back to Pi's built-in summary compaction when pruning cannot free enough context.

Category
Tools & Integrations
Published by
Community
Author
joelhooks
Added
2026-09-22
Tagscommunitytypescriptcompactioncoding-agentagents

Highlights

  • Asks two noul questions per eligible tool call - keep the call and keep its result - then applies keep, drop_result, or drop_call.
  • Keeps the first message and recent messages pinned and filters only the context sent to the model; it never rewrites the JSONL session file.
  • Decisions are stored as append-only fast-jev-decisions entries, and the ledger rebuilds after startup, reload, resume, fork, or tree navigation.
  • Defaults include keepThreshold 0.5, preserveRecentMessages 6, compactAtPercent 60, truncateHeadChars 300, and a minReductionRatio of 0.25.
  • It fails open: a missing key, malformed response, timeout, abort, network error, or insufficient reduction leaves Pi's summary path available.

Quickstart

bash
pi install git:github.com/joelhooks/pi-fast-jev-compaction
pi -e git:github.com/joelhooks/pi-fast-jev-compaction   # one run without installing
export TYPESAFE_API_KEY=YOUR_API_KEY

Watch out

MIT-licensed with the decision core ported from tamaratran/fast-jev-compaction; needs Node 24.18 and Pi 0.85.1 plus TYPESAFE_API_KEY, every ledger edit invalidates the provider's prompt cache from the first edited message, and decisions are model judgments, not proofs.

More like this

6.2kGitHub stars
A Claude Code plugin and npm library that replaces transcript summarization with Jev keep-or-drop judgments, deleting stale tool calls and results while kept text stays verbatim.
Tools & Integrations#community#typescript#claude-code
815GitHub stars
An MCP server and agent skill that verifies coding-agent work by driving the real running app and returning pass, fail, or couldn't-tell verdicts with the file:line to fix; its listing frames the approach as Jev-style machine-native runtime perception.
Tools & Integrations#community#typescript#mcp
Communityreticle
161GitHub stars
A router that turns models, subagents, skills, MCP tools, CLIs, and plugins into one candidate set Jev answers with a single typed Choice, while the router code owns availability, permissions, and confirmation.
Tools & Integrations#community#typescript#routing
CommunityJevRouter
Back to all resources

From the community

Posts from builders shipping with Jev right now.

Follow @typesafeai

Navigating Neo4j with Jev

Jev 这个 waitlist 还是很给力的,昨天申请,今天就能用上。 给已经拿到 API、但还不知道怎么玩的人整理了一份 Awesome Jev,目前我能确认到的 Jev 项目基本都在这里: 1. jev-ultrafast Browser Use 做的高速浏览器 Agent。Jev Show more

Image
思维怪怪
思维怪怪
@0xLogicrw

前 OpenAI 研究员 Diogo Almeida 创办的 TypeSafe AI 推出新模型 Jev。它有点像一个能读懂自然语言的超级分类器,不生成文本,只返回选项、分数和概率,专门给软件做判断。 普通大模型需要一个 token 一个 token 往外生成,Jev 则可以并行给出多个结果。TypeSafe 还用新的 RLCD

Reply

Reranking 33,047 catalog entries

拿 Jev 做搜索重排,我先泼一盆冷水:单独用,它没打赢向量检索 TypeSafe 的 Jev 这阵子很火,一堆项目拿它做重排。我们在 Agent Skills Hub 的 33,047 条目录上认真测了一次,164 条中英文真实查询,9,831 对分级标注,整套只花了 2.6 美元 三个结论 01|单独重排,约等于没赢 Jev 重排 bge-m3 Show more

Jason Zhu
Jason Zhu
@GoSailGlobal

有美团、阿里的老哥嘛? 试试加一路召回、重排(离线、近实时实现),我觉得有奇效 他在文本理解上 跟之前机器学习、llm很不一样 还能自动打标签做特征

Reply

Six uses that stuck after 60 days

Security decisions that fit Jev

This made me rethink where AI actually fits into security engineering. For purely engineering work, forget about ChatGPT or Claude. TypeSafe AI just released Jev, and I think it’s going to change how we build AI into security workflows. Instead of asking an LLM to “investigate Show more

TypeSafe AI
TypeSafe AI
@typesafeai

we are officially out of stealth! join the frontier and get access to Jev on our website (link on profile)

Reply

A million judged questions

Inferring Jev's internals from 1,000 calls

Jevの内部アーキテクチャを推測している技術記事(Jev’s Architecture Unmasked)からメモ。 ・本記事はJevのAPIを約1万回の呼び出して、内部構造を推測したもの ・従来の言語モデルを用いた分類やルーティングでは、トークンを1文字ずつ逐次生成するために膨大な無駄な計算コストが発生していた。 Show more

Reply