Skip to content

Pi Jev Helm

A Pi extension that sends each new unit of work to a Jev client as a paid classification request and routes it to one of four configured Pi models, failing open to your baseline.

Stars
1
Language
TypeScript
License
MIT
Published by
Community
Author
Z761293629
Last verified
Oct 2026

About this project

Pi Jev Helm is a Pi extension that uses Jev judgments — reached through the Jev Client you select, OpenRouter by default — to classify a new unit of work and temporarily select an appropriate Pi model. It reduces manual model switching without taking control away from the user: routing is explicit, configurable, inspectable, and fail-open. If classification or model switching fails, Pi continues with your existing Baseline Model.

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

Highlights

  • Routing is explicit, inspectable and fail-open: if classification or the switch fails, Pi continues on your baseline model and status reports it.
  • With automatic routing on, every new unit of work sends your current message unmodified to the selected Jev client, OpenRouter by default.
  • Route targets resolve exactly against Pi's model registry, with no fuzzy matching or cross-route fallback, so an unresolved target drops to baseline.
  • The recommended install pins an immutable tag at user level, so it loads in every project and the config schema is stable within a minor line.

Watch out

The project labels itself a public preview, pre-stable, with best-effort support and no response-time commitment. Platform evidence is uneven: Linux and macOS have CI and acceptance runs, while the macOS real-Jev gate passed fully in six of nine runs and failed its two-of-three vote on one boundary example in the other three. Windows is explicitly unverified, with no CI, certification or acceptance evidence at all. The extension is fail-open by design, so a routing error silently costs you a baseline-model turn rather than stopping work. A forced kill or power loss that prevents the baseline checkpoint from being written cannot be guaranteed recoverable, and the extension then refuses to apply the route. Pi packages run with full system access, and the configuration file is read at startup and on reload rather than watched. 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.

More Jev resources like this

48GitHub stars
Agent harness for work that outlives one chat, with resumable turns, routed state machines, and observational memory across sessions and processes.
Jev Agents & MCP#community#jevbest#catalog-import
Assistant framework that stores specs, memory, and specialist agents as plain markdown files in your repo for Claude Code, Codex, Opencode, and similar runtimes.
Jev Agents & MCP#community#jevbest#catalog-import
36GitHub stars
Obsidian plugin providing multi-provider chat, vault read and write with function calling, visual workflow automation, and local vector search.
Jev Agents & MCP#community#jevbest#catalog-import
16GitHub stars
Self-hosted OpenAI-compatible router on port 8787 that sends each prompt to the cheapest capable model across free, budget, mid and premium tiers, with heuristic auto and Jev-backed routing modes.
Jev Agents & MCP#community#jevbest#catalog-import
13GitHub stars
Pi extension that classifies each task with Jev over OpenRouter and routes it to a Pareto-optimal model balancing measured quality, cost, and latency under a role policy.
Jev Agents & MCP#community#jevbest#catalog-import
11GitHub stars
Pi Coding Agent extension that routes only at task boundaries, using Jev judgments plus declared capabilities, availability, price estimates, and failure state.
Jev Agents & MCP#community#jevbest#catalog-import
Back to all resources

From the Jev community

Posts from builders shipping with Jev right now.

Follow @typesafeai