OpenJev is a browser-based tool that allows users to run AI models locally and compare different inference methods, such as reading logits directly versus generating tokens in JSON format.
# OpenJev in your browser
Source: [https://openjev.com/](https://openjev.com/)
[openjev](https://openjev.com/)Can we run something like Jev in your browser?[GitHub repo ↗](https://github.com/TheoLeeCJ/openjev)
A live, local experiment
## Decision modelin your browser\.
A local model can either read probabilities for your allowed options without decoding them, or write the same kind of distribution token by token\. Pick a size, run both on your own GPU, and measure the difference\.
browser onlyno backendyour timings1\.56 GB model
**There is no waitlist\!**Just try it out ↓
MiniCPM5 2B is selected by default\. On a phone or smaller device, switch to Qwen3 0\.6B in the model box if needed\.
00 / setup
## Load the model once
Model
Larger model\. Loading may be slower or may not fit on some low\-end devices\.
**Model performance**higher is better
Native BF16 · TypeSafe: same 102\-row subset · Jev: published result · browser builds are quantized
\{\{ text \}\}
download / cache**—**
starts only when you click load
model load**—**download and prepare
warmup**—**compile passes for both methods
Weights come from Hugging Face and remain in your browser cache\. Inputs never leave this page\. First load can take several minutes depending on the selected model, network and GPU\.
01 / decision
## Give it a real choice
Try an example
Both paths receive the same decision\. One reads option probabilities directly; the other asks the model to write its option probabilities as JSON text\.
your decision**state \+ question \+ options**
same local model**MiniCPM5 · 2B**
read logits**A…T probabilities**
write tokens***\{**options**\+**probabilities**\}***
02A / direct readout
## Choice probabilities
no decoding
Read the model’s choice logits and normalize only across the options you supplied\.
waiting for a run
total—input—output1 readout
02B / generation
## JSON probabilities
token by token
Ask the model to estimate the same displayed\-option distribution and write it as JSON\. Watch every token arrive\.
```
waiting for a run
```
first token—total—input—output—
measured wall\-time ratio**run it on your GPU**The methods run sequentially on the same loaded model so they do not contend for one GPU\. Direct runs first, then generation\.
What these numbers do—and do not—mean**Conditional probabilities\.**Direct scores are a softmax over only the displayed option tokens\. They are not calibrated confidence and do not include every answer the model might prefer\.
**Local model tiers\.**The phone model trades accuracy for size\. MiniCPM is the desktop default\. The 4B option needs substantially more memory\. None is claimed to match Jev\.
**Real local timing\.**Setup, warmup, prompt preparation, direct execution, first generated token and generation completion are timed with`performance\.now\(\)`\. No canned results appear\.
**Quantized weights\.**The demo uses pinned GGUF builds through wllama\. Quantization can change both quality and speed\.
The author shares a DIY Jev-like inference setup using open weight LLMs, demonstrating that simple prompting with logit-based verification achieves good accuracy without fine-tuning, and provides a rust web server for local deployment.
The author discusses experimenting with Jev, a tool for AI agents focused on decision-making, which claims significant speed and cost benefits compared to using large language models for all tasks.
Jev is a novel AI model that outputs scores, choices, or binary decisions, praised for its speed, affordability, and accuracy when queried creatively, unlike traditional frontier models.