User repository on GitHub
TypeSafe Jev（System One 决策模型）零依赖网页体验台：浏览器操作 / 意图识别 / Agent 上下文裁剪三大预设场景，发送状态与类型化问题，拿到带校准概率的结构化答案
- Forks
- 1
- Last pushed
- Updated Oct 2026
Repo stats from the GitHub API, cached Oct 2026.Homepage
CommunityJev Demos & Experiments
Jev Demo — PenglongHuang
A zero-build Node server and static page for trying Jev: send a state plus choice, score and noul questions and read back options, scores and calibrated probabilities, with a beta browser agent that drives a real browser through Playwright.
- Stars
- 1
- Language
- JavaScript
- License
- MIT
- Published by
- Community
- Author
- PenglongHuang
- Last verified
- Oct 2026
This is one of several Jev listings for the same project. The canonical entry is Jev Demo — julianoczkowski.
About this project
零构建的本地网页 Demo（无打包、无框架；playwright-jev-agent 那部分需要 playwright-core，见下），用来体验 TypeSafe 的 Jev（System One）决策模型：发一段 state 和几道类型化问题（choice / score / noul），拿回选项、分值与校准概率。. A zero-build local web demo (no bundler, no framework; the playwright-jev-agent part needs playwright-core, see below) for TypeSafe's Jev (System One) decision model: send a state plus typed questions, get choices, scores and calibrated probabilities back.
Quoted from the project's README. Read the full README.
- Languages
- JavaScript
Highlights
- Four built-in scenario pages demo offline; server.js only hosts files and proxies the API, so the browser CORS problem is handled in one place.
- The browser agent gets a goal only: the project builds state and questions, Jev decides each turn and asks for more, with every request body shown.
- The in-process playwright-core backend is the default and falls back to playwright-cli with the reason shown, rather than degrading silently.
- The two order scenarios are a deliberate pair: one spells the steps out for the model, the other hands over a single business intent.
Watch out
You need Node 18 and an API key, and the playwright-jev-agent part additionally needs playwright-core 1.59 or newer plus Chrome or Edge; playwright-cli 0.1.17 is only for the CLI backend. Browser mode matters: the default independent instance leaves your profile alone, but CDP direct-connect drives the browser you already started with remote debugging, so it does touch your session, working only in its own dedicated tab and refusing window-size commands. The API key typed into the page is kept in localStorage, and ALLOW_ORIGIN defaults to a wildcard, so anything beyond localhost wants a reverse proxy with HTTPS. The browser agent is labelled Beta. Saved scenarios and browser sessions are isolated by the first segment of X-Forwarded-For, so a missing proxy header changes who shares a tenant. Copy reviewed against the repository README on 2026-10-04, not from running it.
Questions about this entry
Short answers drawn from the linked project or page.
It depends on the mode you pick. The default independent instance launches its own browser and re-logs in each time with no profile on disk. Persistent login keeps a profile under data/browser-profile/ in a separate process, so it coexists with your daily browser. CDP direct-connect attaches to the debugging browser you already started, which does mean it operates inside your session, though only in a dedicated tab it creates itself and never resizes the window.
You usually would not. Each CLI command spawns a new node process, spending roughly 0.8 to 1.0 seconds just loading playwright-core with no persistent channel, and the README's own measurements put a page-state read at about 3900 ms and a page open at about 7800 ms against 65 ms and 14 ms for the in-process backend, with act at 719 ms. It exists as a fallback: if the in-process path cannot start, the app switches to the CLI and tells you why on screen.
A demo, deliberately. There is no bundler and no framework, npm install pulls only playwright-core, and node server.js hosts a static page plus the API proxy, scenario saving and driver wiring. The four built-in pages work offline. Testing is node:test unit tests plus a real playwright-cli smoke test that skips when the engine is unavailable, and an Auto-mode end-to-end run that defaults to a local oracle and can be switched to real Jev.
server.js takes the first segment of X-Forwarded-For, hashes it with SHA-1 and writes under data/, so backing up that directory backs up everything. That only works if something is actually setting that header, which is why the README recommends running behind nginx or caddy with HTTPS and passing X-Forwarded-For. Left on its own, ALLOW_ORIGIN defaults to a wildcard, which is fine for localhost and wrong for anything else.
It is zero-build, so no bundler or framework is involved: npm install (which only installs playwright-core for the in-process driver), then node server.js on Node.js 18 or newer. Open http://localhost:3000 and paste a TypeSafe API key at the top of the page.
Paste it in the page and it stays in localStorage without touching disk, which the README recommends. Alternatively set TYPESAFE_API_KEY as a server-side fallback; the page value takes priority when both are present.
Independent instance is the default and logs in fresh each time with no profile persisted. Persistent login stores the profile under data/browser-profile/ after one manual login. CDP direct connects to your existing debug-port browser and does touch it, though it only operates in its own new tab.
More Jev resources like this
11GitHub stars
Agent skill that ports the ultrafast browser loop into ego lite: ego executes while Jev picks the operation and target in one call per step, with escalation instead of guessing on risky actions.
Jev Demos & Experiments#community#awesomejev#catalog-import
Community
ZephyrDeng/ego-jevTypeScript
ZephyrDeng/ego-jevTypeScript3GitHub stars
Browser agent where Jev makes every navigation decision and agent-browser performs clicks and typing, stopping when the named goal page is reached or blocked.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
kyrylosyzonenko/jev-browseJavaScript
kyrylosyzonenko/jev-browseJavaScript5GitHub stars
An MCP server that lets Claude or Codex drive a real Chrome window: Claude plans the task and Jev picks each click, keystroke and scroll from a numbered element list, with irreversible actions held for confirmation.
Jev Demos & Experiments#community#awesomejev#catalog-import
10GitHub stars
Playwright wrapper that routes natural-language operations and assertions through Jev while clicks, typing and waits stay deterministic, with verification provenance.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
tontoko/jev-browserJavaScript
tontoko/jev-browserJavaScript2GitHub stars
A skill and MCP server that drives a real browser for coding agents. One Jev request per step picks the action and the target, and the control loop stays in code.
Jev Demos & Experiments#community#awesomejev#catalog-import
Community
ChenYCL/jev-browser-skillJavaScript
ChenYCL/jev-browser-skillJavaScript2GitHub stars
Three dependency-free files that put Jev in a browser agent's hot path: code builds the choices from a table of visible controls, Jev picks an operation and target in one forward pass, and the code executes the pick.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
zurfyx/jev-browser-skillJavaScript
zurfyx/jev-browser-skillJavaScriptFrom the Jev guides
Original write-ups on what this entry is for.
A game tick is a state plus a legal action list. How Clash Royale, Minecraft, and the earlier Mario, Pokémon, StarCraft, and drone loops ask Jev one step at a time.
Jev Demos & Experiments#gaming#agents#control
Read article
From the Jev community
Posts from builders shipping with Jev right now.