Will this actually cut my token usage?

Not broadly by its own account: a source-read experiment reduced returned text but added tool calls without consistently lowering total input or latency, so keep uncertain evidence and watch capability regressions before assuming savings.

Can the sieve hide a failing test?

It is built not to: deterministic guards retain failures, warnings, stack regions, diagnostics, summaries, task terms, and uncertain blocks, failed commands need recognizable failure evidence, and only separate PASS-only blocks may hide.

What happens when Jev is unconfigured or fails?

Output passes through unchanged with no replacement marker: missing keys, network or timeout errors, malformed answers, parser and budget failures, and original-persistence failures all preserve the full result.

How do the mode, dedupe, and sieve switches interact?

Each layer resolves from options config, environment, settings file, then compatibility mode, with explicit session overrides persisting per branch; mode alone is not a master switch, so set both layers off explicitly to disable them.

How do I turn the dedupe and sieve layers on or off?

They are independent. /context dedupe on|off and /context sieve on|off are session overrides, with environment switches PI_JEV_CONTEXT_DEDUPE and PI_JEV_CONTEXT_SIEVE and a settings file at ~/.pi/agent/pi-jev-context.json. /context mode is not a master switch.

How does the recall tool find saved originals?

context_recall searches branch-local saved originals by deterministic keyword and identifier overlap with an exact-phrase bonus, returning ranked verbatim chunks with original line numbers and source ids. Chunks target 24 lines with an 800-token search budget, and no embeddings or Jev call is involved.

Which commands is the Jev sieve allowed to process?

Only long, text-only bash results with an unambiguous test, build, lint, typecheck/diagnostic or explicit log command. It recognizes forms like python -m pytest, cargo check, cargo clippy, go build and go vet, and failed commands are eligible only when they contain recognizable failure evidence and PASS lines.

CommunityJev Agents & MCP

Pi Jev Context — Nyarlathoteppppp

Pi context extension that folds repeated reads, filters long command logs through Jev, and retrieves saved originals as searchable verbatim chunks.

See highlights

Open github.com

Stars: 10
Language: TypeScript
License: MIT
Published by: Community
Author: Nyarlathoteppppp
Last verified: Oct 2026

Nyarlathoteppppp/pi-jev-context

User repository on GitHub

View on GitHub

Model performance first. Token savings second. A Pi extension with freshness-aware read dedupe, Jev log filtering, and searchable verbatim recall. Keeps existing message history intact.

Forks: 0
Last pushed: Updated Sep 2026

Repo stats from the GitHub API, cached Oct 2026.

About this project

Less noise. Original evidence within reach. A context extension for Pi that folds repeated reads, filters long command logs with Jev, and retrieves saved originals as searchable, verbatim chunks. Independent switches. Branch-local originals. Pi-native compaction.

Quoted from the project's README. Read the full README.

Tagscommunity jevbest catalog-import awesomejev

Works forJev for Classification Jev for Moderation

Used inJev for Software & DevTools

Languages: TypeScript

Highlights

Deterministic dedupe folds only exact repeated file lines while the source stays fresh, visible, and in-epoch.
Jev sieve filters eligible long text-only command logs while hard KEEP rules and failures preserve original output.
Recall searches branch-local saved originals by keyword with source IDs, line ranges, and a retrieval budget.
Layers resolve independently with session overrides, threshold and token knobs, and Pi-native compaction behavior.

Watch out

Broad efficiency gains are not established and recall is an escape hatch rather than proof of preserved capability; every judgment or persistence failure returns the full output. Copy reviewed against the repository README on 2026-10-04, not from running it.

Questions about this entry

Short answers drawn from the linked project or page.

Other listings of this project

Forks and copies of this project in the directory. This entry is the canonical one.

pi-jev-context

Pi extension that uses Jev to judge which older session messages are still worth sending to the model, hiding low scorers from future requests while leaving the session transcript itself intact.

Jev Agents & MCP#community#awesomejev#catalog-import

Community

kevinpita/pi-jev-contextTypeScript

More Jev resources like this

jev-test-filter

Diff-aware test selector that sends the git diff to Jev with one question per test, then prints the native filter flags and hands them to vitest, jest, node, bun, Playwright, cargo, or go test.