Local service for authoring versioned judgment functions on TypeSafe Jev in a browser, then publishing one immutable version that both your backend calls over HTTP and your coding agents call over MCP, using a scoped client token.
Organization repository on GitHub
Build versioned judgment functions on TypeSafe's Jev once, then call the same published version from your backend over HTTP and from coding agents over MCP. The vendor key stays on your machine.
Repo stats from the GitHub API, cached Oct 2026.
Write a judgment once. Call it from everywhere. Jev Workbench is a local service for building judgment functions on top of TypeSafe's Jev — small, versioned decisions like "is this ticket about billing?" or "does this evidence support that claim?". You define one in the browser, try it on real input, and publish it. From then on the same published version answers both your backend over HTTP and your coding agents over MCP.
Quoted from the project's README. Read the full README.
Watch out
Requires Node.js 24 and pnpm 11.9.0. The demo on port 17430 serves simulated answers with no network and is not evidence that a production publish will work. Without a TypeSafe key you can still edit everything but inference returns PROVIDER_NOT_CONFIGURED, and production never falls back to simulated answers. It binds 127.0.0.1:17420 only. POST /v1/systemone and GET /v1/models need an explicit Allow official Jev calls setting, and the official Python SDK works against it only if the token has that access. Each agent install writes its own credential file at mode 0600, and uninstall stops if the entry was hand-edited. Copy reviewed against the repository README on 2026-10-04, not from running it.
zjunlp/JevLoopTypeScript
tyler-dot-earth/patdownTypeScript
Nasrallah-AL/jev-cliTypeScript
Brainwires/jevwireTypeScript
HyunjunJeon/pi-quiet-askTypeScript
rashedInt32/jev-mcpTypeScriptPosts from builders shipping with Jev right now.