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.
Same 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.
311 experiments · showing 241–300
An OpenAI- and Anthropic-compatible gateway where a small System One model picks which larger model should answer each prompt.
An MCP server and agent skill for using System One at design time: decompose a judgment into questions, lint them, calibrate thresholds on labelled rows and rerank.
A local agent harness that puts Jev in front of an ordinary LLM and pays for the LLM only when the work needs prose.
A coding-agent CLI that splits the work: a decision model picks the next tool, scores progress and judges whether the goal is reached, while an LLM only fills in arguments and writes code.
Gates agent tool calls through detectors, Jev judgments, and deterministic policy before allowing, blocking, or requesting approval.
Reads completed Claude Code or Codex sessions and assigns typed judgements to each turn for later analysis.
Put many MCP servers behind two tools while Jev discovers the best enabled tool and the calling agent supplies its schema-bound arguments.
A Rust CLI turns Jev judgments into stable JSON, resumable batches, assertions, and meaningful shell exit codes.
A small CLI ranks local Agent Skills against a request, then returns suggestions without invoking anything automatically.
Add three Claude Code hooks that flag dangerous commands, failed tool calls, and incomplete work with Jev.
Screen fetched pages and files for prompt injection before coding agents load them, blocking content that crosses configured thresholds.
Check each coding-agent edit against a team style guide and send violations back into the session.
Riley Brown put Jev behind an agent’s model router to choose which model handles each task.
ImRobot’s hook-based gate blocks dangerous agent commands until a person approves that single execution.
Milind S added Jev to OpenMausBot to choose both the teammate and model for each task.
Cyril split agent work so Claude Code writes while Jev handles repeated decisions on suitable tasks.
Jetwani Avinash’s Claude Code gate asks Jev whether each message deserves one line in a repository memory file.
Paulius used Jev to launch agents on Clonk’s visual canvas without waiting for a full LLM loop.
Kelbie built a Jev tool that scores every code chunk for relevance to a developer’s current question.
Cortex is a local MCP server where Claude plans tasks and a faster action layer handles clicks across browsers and Mac apps.
Oskar is building an open-source framework that uses agents and Jev to run end-to-end tests across web and mobile.
grok-jev-reflex is an open-source router where Grok plans and acts while Jev handles cheaper yes-or-no decisions between steps.
Ishwar demonstrates instant Jev compaction during a long Claude Code server-redeployment session.
Action Gate asks Jev to score risky agent actions and routes a simulated $50,000 transfer to human review.
jev-studio packages Jev’s three primitives as MCP tools and a CLI with dry-run provenance.
Monid connects Jev and OpenRouter to a catalogue of tools for lead scoring, research, content analysis, and site audits.
Kiyoro used Jev to detect that Opus 5.5’s default effort had changed from high to medium.
Sawyer Hood uses Jev to choose an agent, model, computer and working folder from a single prompt.
Neha Sharma built a real-time demo that uses Jev to route work among AI agents.
erKam built a Jev check that quotes violated project rules back to Claude Code so it can rewrite its response or edit.
Jev chooses a skill, tool, and parameters before a Slack agent acts, which its maker says doubled its speed.
Jev directs a coding agent toward relevant files and flags possible test gaps, while deterministic tests verify the result.
Read browser-agent activity logs every three seconds and average the resulting risk score across the session.
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.
Docker Agent asks Jev whether a pending tool call is clearly read-only or needs the user's approval, treating uncertain calls cautiously.
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.
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.
mem-jev asks Jev to judge ambiguous agent memories, then folds five semantic signals back into retrieval ranking.
Keel can ask Jev which installed coding provider and model should receive a new task.
Record live Jev decisions as redacted cassettes, then replay or perturb them without another provider call.
Add Jev-backed tool approval, chat triage, transcript curation, and model routing to OpenClaw.
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.
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.
An ACP and MCP adapter that hands Jev's three typed question types to any LLM agent, built for Roblox computer use.
When the robot acts up, Jev plays detective: it chooses which diagnostic tool to run next, while the tools themselves stay plain deterministic code.
Points a debugger at your bug and lets Jev decide every next step, so the expensive model only wakes up for the hypothesis and the fix.
Keeps a record of what you and your coding agent agreed to build, in plain Git commits where the next session can find it.
Watches what you type into Claude Code and decides who should handle it: your slash commands go straight through, everything else gets checked against your rules.
Semantic lint rules written as plain-English yes-or-no questions, with Jev returning a calibrated probability instead of free text.
One Jev call before every commit checks that your message actually describes the diff, and flags debug leftovers and pasted secrets while it is at it.
Gives the Pi coding agent a Jev-powered tool for the small stuff: classify this report, triage those issues, score these candidates, all in one batched call.
A Python library that reranks and relevance-filters RAG retrieval with Jev, scoring documents for how much they help answer the query.
A Go reverse proxy that sits between nginx and your LLM backend, judging every request's user input with Jev and blocking harmful traffic transparently.
A semantic code linter that judges your source against configurable plain-language rules and prints per-finding confidence.
A chaperone for agents doing web research. Nothing gets fetched or trusted without Jev weighing in on it first.
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.