Read & learn
Written guides.
Understand Jev, one idea at a time. Walkthroughs, recipes, and writeups — our notes first, the original next.
Learn, build, and play with Jev — from deep technical guides to creative experiments.
Read & learn
Understand Jev, one idea at a time. Walkthroughs, recipes, and writeups — our notes first, the original next.
Watch & learn
See an idea take shape. Tutorials, demos, and deep dives, organized by topic and credited to their creators.
Make & explore
See what builders made with Jev. Games, tools, repositories, articles, and more — traced to their sources.

Every category, from games and tools to repositories and writeups, traced to a primary source.
Real-time research powered bySame ideas.
Different paths.
This is the full registry, not just the featured picks. Figures like speed, cost, and stars are maker-reported or captured snapshots, not JevMade measurements.
2140 experiments · showing 1681–1740
Find community Jev systems through their typed questions, with source snippets and maker posts alongside each listing.
Speak a voice diary, let Jev sort your thoughts, then review the notes, tasks and reminders before sending them to Notion.
Search an English–Icelandic dictionary by meaning, with Jev checking whether the shortlist contains a match and ranking the results.
Bring Jev Search's ranked links into Claude Code, Codex or a terminal through an MCP server, CLI and optional WebSearch hook.
Play Pong against Jev and watch its movement, shot selection, probabilities, and fallbacks in a live decision monitor.
Four ways of asking Jev to play 2048, compared with random moves and fixed rules, with replays of the resulting games.
OpenRouter's Jev Router picks the model and reasoning effort for each request, and holds a model while its prompt cache stays warm.
OpenCodex asks Jev to choose a model and reasoning level for each Codex request, using the proxy's configured route whenever Jev is unavailable or returns an invalid answer.
A Phoenix Evals example pits Jev against a small grounded-versus-hallucinated answer benchmark.
Docker Agent asks Jev whether a pending tool call is clearly read-only or needs the user's approval, treating uncertain calls cautiously.
GPTCache asks Jev whether a cached answer still fits a new request, taking differences in the requests, answer, and dates into account.
Agent Native asks Jev which optional tools an agent should see at the start of a request, based on the user's recent context.
Memorax asks Jev whether searching saved coding memories would materially help with the current prompt and, when available, the previous turn.
Interactive Shell uses Jev to decide when terminal work needs attention and which pre-authorized action may help.
haiku.rag provides a reusable System One judge for benchmark verdicts such as whether two answers are equivalent.
Kimaki's OpenCode auto-mode asks Jev whether a pending tool action may run without another prompt, using the action, its arguments, and the latest user message.
ctx sift uses Jev to keep useful or contradictory passages while shrinking an agent's tool output.
TypeSafe Jev Gate adds a fail-closed review step to Hermes Agent's consequential tool calls.
Lintus turns plain-language YAML rules into Jev checks and reports threshold-crossing answers as lint offenses.
Search a retained window of Kubernetes or file logs with Jev, then inspect matching, possible, and unrelated evidence.
mem-jev asks Jev to judge ambiguous agent memories, then folds five semantic signals back into retrieval ranking.
Mistype a subcommand and jevyoumean asks Jev which documented command you probably intended.
A JevNPC trial asks whether a threatened Minecraft villager should ignore danger or call the guards.
Keel can ask Jev which installed coding provider and model should receive a new task.
Triage messages, classify CSV rows, interpret voice commands, or let Jev steer Snake from a Java web playground.
Send text through a named semantic rule or your own question and receive a valid, invalid, or uncertain result.
Record live Jev decisions as redacted cassettes, then replay or perturb them without another provider call.
Watch Jev choose a legal Tetris placement from a heuristic shortlist, then play the selected move.
AutoNomousBot shows Jev a Minecraft world snapshot, lets it choose from available actions, then performs the selection.
Give Jev Pilot a mobile goal and it observes the screen, chooses a bounded UI action, and performs it.
Add Jev-backed tool approval, chat triage, transcript curation, and model routing to OpenClaw.
TweetGuard uses Jev to sort individual X posts into spam categories while leaving uncertain posts visible.
DLQ Inspector asks Jev whether an ambiguous dead-letter message should be replayed, fixed, avoided, or investigated.
Any Auto asks Jev whether coding-agent tool calls are risky, authorized, and policy-compliant before approving them.
Supercov asks named quality and security questions about source files, then turns Jev's answers into inspectable findings.
Sentio classifies email with Jev and adjusts spam scores from unsolicited-mail and phishing probabilities.
Run Laya’s typed decisions natively on Apple Silicon, then watch its terminal Snake demo choose moves with safety corrections.
Josh Rosen rounds up the first two weeks of JevOps — decision-model calls showing up in telemetry, incident response, SRE agents, CI, and deploys — and argues DevOps is packed with exactly the small semantic judgments Jev is built for.
Does Jev hold up outside demos? Glean's team benchmarked it on four workloads they run in production and published the wins next to the losses — routing came out ahead of their LLM router, reranking did not beat their search stack.
The weekly How I AI digest leads with Claire Vo spending a week inside Jev: nine cents to make sense of two years of ChatPRD pull requests, about four dollars for 200,000 classifications, and a working answer to which tasks still deserve a frontier model.
Claire Vo opens the hood on her week in Jev: nine cents to classify two years of ChatPRD pull requests, her Claude and Codex sessions sorted in minutes, and a real-time voice app where the quote API, not the decision model, was the slowest part.
Two days after Jev launched, Cribl's AI Research team published a grounded early look at what decision models can and cannot do inside a telemetry pipeline, benchmarking Jev against the purpose-built classifiers and LLM judges they already operate.
Most log records never need a language model's opinion, so Jev Logs scores each one first: how diagnostically useful it is, how urgent, and whether deeper analysis is warranted. Only confident, low-value records skip the expensive branch, and the archive always gets everything.
jevbrief fixes the least glamorous part of a Jev integration: what the model actually gets to read. Adapters for CI runs, pull requests, OpenTelemetry exports, and other noisy sources cut state down to what matters, and every dropped line gets a reason.
jevtraces brings the same annotation idea to spans: an alpha OpenTelemetry processor asks Jev whether an operation looks worth diagnosing, whether it's business-critical, and whether to keep it, then caches the verdicts and stamps them on later matching spans. Every span is retained regardless.
Datadog's Agent Observability team shows Jev doing double duty in their eval stack: notebooks score production agent spans as they arrive through online evals and run the same focused questions offline, mapping typed answers onto Datadog metrics.
SREGym gave its incident-solving agent a hesitant reviewer: before any diagnosis gets submitted, Jev has to agree the evidence supports it, and when a test is proposed, Jev ranks which one is worth running first. Pass rate moved from 20 to 24 out of 50.
jev-oncall routes production alerts with one typed Jev call per alert, then lets boring, auditable code decide what the probabilities are allowed to do. The model judges; a page threshold, a review band, and a fail-open default do the rest.
A confidence-gated incident router that consults an ownership registry first and Jev only when routing needs interpretation: choice picks the response team, score places business impact, noul estimates blocked critical work, and low confidence routes to human review instead of action.
A security-operations experiment set that runs Jev as a first-line decision layer across SOC work: phishing classification, authentication triage, BEC detection, investigation routing, and prompt-injection detection, with a unified PhishGuard pipeline and an eval suite of staged states.
jev-ci-pathfinder lets Jev decide which optional CI jobs a change actually needs, one allowlisted job at a time. Always-on jobs, path rules, and dependency closure never leave code, and when Jev is unavailable the action runs its configured conservative set rather than guessing.
This canary-rollout demo keeps the state machine in charge: it decides which transitions exist, Jev weighs evidence only at model-eligible branches, and the captured run holds at 5% traffic before promoting as evidence firms up.
A demo incident-response agent that puts the loop in Temporal and the judgment in Jev: typed next-action choices, a severity score, and safety probabilities drive durable activities, with retries, worker crashes, and a human-approval signal all surviving restarts.
A red-team of Jev 1.13 got it to approve harmful tool calls 70.1% of the time under direct misuse and 43.5% under indirect injection. The fix has a nice shape: Jev re-judges its own tool calls before they run, and both attack rates roughly halve.
Agent payments settle in milliseconds, and x402check spends that instant asking Jev six questions about the payer: known threat, sanctions, laundering, lookalike domain, operation class, trust. Every verdict ships as a signed attestation, so the check is provable, not promised.
Jevry browses for you one Jev choice at a time: it plans a site's steps first, then walks them with deliberately boring automation.
An ACP and MCP adapter that hands Jev's three typed question types to any LLM agent, built for Roblox computer use.
One Minecraft body with a split brain: GPT-6 Astra plans, and Jev answers action, safety, and urgency in a single parallel call.
CartPole, MountainCar, Acrobot, and FrozenLake trained with reinforcement rewards that come from Jev's calibrated scores instead of a hand-written reward function.
Freedoom, ViZDoom, and a decision model that has never held a shotgun: the dashboard plays Jev's run back with a dollar figure next to every call.
Jev, briefly
A chat model generates text token by token and hopes you parse it. Jev never generates a word. Your code sends the state of the world plus typed questions; Jev returns every answer in one parallel pass — typed values with calibrated probabilities and a confidence score your code can trust. About 70–500 ms end to end, $0.042 per million input tokens, output free. Trained with what TypeSafe calls Reinforcement Learning for Calibrated Decisions.
You define the options. Jev returns the chosen option, a probability for every option, and a confidence. The workhorse of routing, agents, and games — the answer space is always legal, so there is nothing to parse and nothing to hallucinate.
You describe ordered levels — say trivial / normal / critical. Jev returns the level, the probability of each, and a confidence. Scores turn fuzzy judgment (“how severe is this log line?”) into a number-free decision your code can branch on.
You assert a statement; Jev returns the probability that it is true — a noul. Moderation, verification, guardrails, “does this diff actually fix the bug?”: one question, one calibrated probability.
Official material lives at typesafe.ai and docs.typesafe.ai. JevMade is an independent community registry — not affiliated with or endorsed by TypeSafe AI.
Recurring lessons
Games, drones, trading bots, and browser agents all converge on the same loop: serialize the state, ask one decisive question, act, repeat. Jev’s latency makes the loop feel instant — the model lives inside the control loop, not outside it.
The answer says what; the confidence says whether to act. The most reliable entries threshold on confidence to route edge cases to a slower model or a human — automation with an honest escape hatch.
Makers rarely ask Jev to pick from everything. Local tactics prune 225 gomoku moves to ~40; DOM filters turn a page into an element table; code narrows options, Jev judges within them.
A recurring split: Jev makes every decision cheaply and instantly, and a small LLM is only invoked when a human-facing string must actually be written. Decision and generation are separate budgets.
Send the link — repo, live demo, post, or video — plus a line on what it does and which primitives it uses. Every entry is verified against its primary source before it ships.
Submit your experimentSign in first so we can reply to you. Submissions are reviewed, not published automatically.