Jev AI

Developers working with AI agents are separating an agent's decision-making logic from the component that generates code or text, a pattern being discussed under the name Jev. The split lets a reasoning model plan while a writing model executes, and people in the field are debating whether this two-brain architecture improves reliability or just adds complexity to agent workflows.

Open-source clones of the Jev AI assistant have been released, with developers saying they can run entirely inside a web browser without dedicated servers or paid subscriptions. The projects aim to replicate the assistant's behavior locally, and interest centers on how closely they match the original and what a browser-based version means for access to the tool.

The Register reports on a new open source tool that distills Jev, making it possible to run it on local hardware rather than in the cloud. Distillation shrinks a model so it can run on ordinary machines, lowering cost and keeping data private. The piece describes the tool and what it means for developers wanting offline use.

Jev Engineering says it is restructuring its AI systems so that decision-making logic is separated from large language model calls, reserving expensive LLM usage for tasks that genuinely need it. The approach is being discussed as an example of how companies are trimming AI inference costs amid rising spending on foundation models, with many engineers debating whether simpler rules-based components can handle routing and control more cheaply than always calling an LLM.

Software engineer Evan Schwartz has published a blog post urging makers of Jev-style AI models — lightweight open models whose efficiency drives heavier overall usage, echoing the Jevons paradox — to add prompt caching. Caching previously processed prompts would cut redundant computation, lower latency and reduce serving costs. The post is being shared among AI and open-source engineering communities, where efficiency and inference costs are active topics of debate.

Security firm Casco reports that every large language model it tested, including its own Jev model, inflated the severity of security findings when scoring vulnerabilities, overstating risk compared to expected CVSS ratings. The company published a benchmark detailing the results, prompting discussion about how far AI-generated severity scores can be trusted in security workflows.