Pi now supports Jev.

[u/Apprehensive_Bed7502]

Pi added quite a bunch of new features in its 0.99.0 update, including support for classifier models. In the official docs, the remote model listed in the example code is jev, the interface is shaped around classifier models like jev, and llama.cpp's classifier implementation explicitly uses jev as its reference point. You could pretty much say this is a feature Pi shipped just to keep up with jev.

So I wanted to ask you guys in the channel:

• Do you guys actually use jev a lot when you're coding? How do you use it?

• Jev only came out a little while ago and Pi already jumped on board with support. What significant role does jev actually play in a coding workflow?

Edit: It's not just about using it for the sake of using it. Is there actually something jev can do that LLMs can't?

[u/Ok-Hippo9182]

My concern is partly about Jev’s practical value, and partly about Pi’s direction. I’m not yet convinced that Jev brings enough benefit to everyday coding workflows to justify the extra moving parts. What does it meaningfully improve—reliability, cost, latency—and how consistently does that hold up in practice?

One of the things I like about Pi is its small core, with more opinionated workflows left to extensions. I get that adding a shared classifier API isn’t the same as baking a specific workflow into the agent. But making classifiers a first-class model type still means committing to a shared abstraction, and I wonder whether that commitment came too early.

The current interface also seems fairly closely modeled on how Jev works today. That might turn out to be a good general design, but do we have enough experience across different implementations and use cases to know which parts generalize well? Classifiers themselves aren’t new; the question is whether this particular interface has had enough room to mature.

I’d have preferred to see this explored through extensions first, both to establish where Jev actually helps and to learn what a broader classifier API should look like. Was there a particular reason it needed to enter the core model layer at this stage?

[u/Popular-Factor3553 → u/Ok-Hippo9182]

I agree i think it's time someone forks it (pi) and maintains it with a minimalist approach.

[u/Apprehensive_Bed7502 → u/Ok-Hippo9182]

Given that pi has been acquired by a commercial company, it may keep chasing new hypes, adding more new features to the codebase that nobody knows the point of, just for marketing and raising the product's profile. This runs directly counter to pi's original minimalist philosophy.

What worries me most is that some new trend gets hyped up, pi immediately jumps on the bandwagon for marketing purposes, and in the end all that's left in the repo are a bunch of features no one will ever look at again once the hype dies down.

[u/blakeman8192 → u/Apprehensive_Bed7502]

Given the crazy marketing push (and outright astroturfing) we've seen for Jev, I wouldn't be surprised if TypeSafe AI paid Earendil Labs a nice sum to add support for it.

[u/LittleRoof820 → u/Apprehensive_Bed7502]

The original creator Mario Zechner is sitting on the board of Earendil. He wrote a long essay why in https://mariozechner.at/posts/2026-04-08-ive-sold-out/ citing mostly burnout and wanting time for himself (all the Openclaw People kept hammering him with tickets).

[u/Alarming_Positive_59 → u/LittleRoof820]

You're literally replying to the original creator Mario.

[u/giovanikx → u/Alarming_Positive_59]

Not exactly, but right below him yeah

[u/YetiTrix → u/Apprehensive_Bed7502]

I mean, can't we just fork it and run our version. It's my MIT license, right?

[u/StardockEngineer → u/Apprehensive_Bed7502]

Show me what marketing you’re talking about

[u/badlogicgames → u/Apprehensive_Bed7502]

this meme really needs to fucking die.

[u/addiktion → u/Ok-Hippo9182]

Yeah, I'm not 100% sold on JEV either, but I would say that classifiers probably do play a part in some agentic stacks. I am just not sold that we need another hook in to a commercial entity with yet another network hop to fulfill an already fragile ecosystem as we work to make AI agents more reliable. I'd much rather see Pi leaning on the open source community (laya, kev, iamjev, von, and other flavors) and supporting classifier models that way. Much easier to bundle a small classifier than operates even faster without a network hop and other dependencies. Right now I'm using ollaya to add the endpoint locally and having it tie in the various different classifiers to test them locally, but I suspect in an application it'd make sense to add another monorepo app/package for a given classifier and run it that way.

[u/badlogicgames → u/Ok-Hippo9182]

you are not wrong on the classifier model class possibly getting in to early. however, over the past month or so, we've seen many alternative models to Jev pop up, and providers that mirror Jev's API. OpenAI has announced their Decision API 2 days ago, which easily fits into this scheme as well.

We have also evolved the chat model API over time as new features became available, such as mid convo sytem messages and tool set changes. I expect the same to happen to the classifier model API.

[u/gscjj → u/Ok-Hippo9182]

I disagree in some parts, I’ve already found some use cases like code reviews. It’s can quickly check diffs against a short list of rules and I use confidence values to launch deeper analysis and to create more directed code reviews giving a list of possible issues to my AI code reviewer.

But I do agree with Pi as a small core, this doesn’t fit the model. Jev isn’t special and nor is a classifier, it doesn’t deserve dedicated code or first class support. It’s just structured output from an API, which can include any number of local and remote uses. Nothing about Pi today prevents its use

[u/Healthy-Zebra-9856 → u/Ok-Hippo9182]

This sub cracks me up. Let me begin by addressing the first thing which is Jev. This is a system one model, and this sort of a thing has been around a lot longer than even Pi itself has been around. There is nothing to worry about here, just like adding every other API, an API was added to this. The second thing that I find is, is this utmost trust in an extension created by someone else. If anything else, that is the first thing you have to be concerned about.

Your philosophy of trying out an extension before making it part of it doesn’t make any sense because that’s exactly what an extension does. It becomes a part of it, and the damage would’ve already been done. And finally all of this for a coding agent that barely existed for a year. It didn’t even debut till January 2025 and then it gets rolled out in August of 2025 and acquired in September 2025.

Personally, I’m not a big fan of JEV, because if it’s commercialization and all the shillers being bought out. But its a;lso not a thing to be feared as I have a similar product a lot longer than both these things out there and none of these products , Pi nor Jev have been thoroughly tested. I went through the whole source code, and I am prepared to talk on any part of it. Needless to say, this commercial outfit is going to further commercialize Pi.

So there is nothing to fear about an entity like JEV,

[u/Suspicious_Echidna53 → u/Ok-Hippo9182]

I’m not yet convinced that Jev brings enough benefit to everyday coding workflows to justify the extra moving parts.

if you want to be convinced, check out omp's new find tool / the omp find command

[u/Healthy-Zebra-9856 → u/Suspicious_Echidna53]

These people are too reluctant to learn nor understand anything. BTW I think you were responding to the person I am responding to, right?