User repository on GitHub
Two Jev agents duel at Snake via Vercel AI Gateway.
- Forks
- 0
- Last pushed
- Updated Sep 2026
Repo stats from the GitHub API, cached Oct 2026.Homepage
CommunityJev Demos & Experiments
JevArena — rolki-png
A Next.js spectator app where two independent Jev agents play Snake against each other, each spectator page running its own match. Jev is reached only through Vercel AI Gateway, and an empty key gives you a labelled demo-policy match instead.
- Stars
- 0
- Language
- TypeScript
- License
- MIT
- Published by
- Community
- Author
- rolki-png
- Last verified
- Oct 2026
This is one of several Jev listings for the same project. The canonical entry is Jevarena — chenmingtang830.
About this project
A spectator arena where two independent Jev Agents play Snake against each other. JevArena is a public Next.js app: Landing at /, then the Arena. Each Spectator's page runs its own Match. Jev is reached only through Vercel AI Gateway. Open The Landing explains the Match; Enter the Arena opens /arena with two isolated Snake Browsers.
Quoted from the project's README. Read the full README.
- Languages
- TypeScript
Highlights
- Two isolated Snake browsers per match, opened from a landing page that explains the match first.
- Each spectator page runs its own match rather than watching one shared simulation.
- AI_GATEWAY_API_KEY is the only credential, it stays on the server, .env.local must never be committed.
- Standard scripts: tsc --noEmit typecheck, ESLint, Vitest tests, plus build and start on port 43123.
Watch out
This is the thinnest README in the batch - a little over a thousand characters - and it is an index-level description, so a lot is simply not documented: no questions are shown, no Jev primitives (Choice, Score or Noul) are named, there is no timing or decision frequency, no latency or cost per match, and no description of what each agent actually decides or how the two Snake browsers are isolated from each other. Nothing is said about match length, scoring, or how the two agents differ. The tests are listed as a command with no coverage or assertions described. Crucially, with an empty AI_GATEWAY_API_KEY you are watching a labelled Demo policy match, not Jev, so a first run tells you nothing about model behaviour; and if Jev fails with a key set, that agent is BLOCKED and the Demo policy does not run in that case, leaving a dead side rather than a fallback. It is described as a public Next.js app but no deployment or hosting instructions are given. 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.
Not documented. The README says only that two independent Jev agents play Snake against each other, that each spectator's page runs its own match, and that Jev is reached only through Vercel AI Gateway. There is no question set, no mention of Choice, Score or Noul, no decision frequency and no description of what distinguishes the two agents, so you would be reading the source to answer this.
Yes, by leaving the value empty. Copy .env.example to .env.local and leave AI_GATEWAY_API_KEY blank to watch a labelled Demo policy match; set it and both agents are driven by Jev through Vercel AI Gateway. One catch worth knowing: if Jev fails, that agent is BLOCKED, and the Demo policy does not run in that case, so a failure with a real key set leaves you with a blocked agent rather than a fallback.
The key stays on the server - AI_GATEWAY_API_KEY is the only credential and .env.local must never be committed. Each spectator's page runs its own Match rather than watching a shared simulation, which is the stated design, though the README does not explain how the two Snake browsers are isolated from each other.
The README calls it a public Next.js app with a landing page at / and the arena at /arena with two isolated Snake browsers, but gives no deployment or hosting instructions. Locally it is npm install, copy .env.example to .env.local, npm run dev, then http://127.0.0.1:43123. Verification is npm run typecheck, npm run lint, npm test under Vitest and npm run build, with no description of what the tests cover.
A public Next.js application: the landing page is served at / and the Arena at /arena, which opens two isolated Snake Browsers and runs a separate match per spectator page. Jev is reached only through Vercel AI Gateway, and the project is MIT licensed.
npm run dev serves on port 43123, npm run typecheck runs tsc --noEmit, npm run lint runs ESLint, npm test runs Vitest unit tests, and npm run build and npm start produce and serve the production build on port 43123.
A lot: no question set or Jev primitives (Choice, Score or Noul), no timing or decision frequency, no latency or cost per match, and no description of what each agent decides, how the two Snake browsers are isolated, match length, scoring, or how the two agents differ. Answering those means reading the source.
More Jev resources like this
38GitHub stars
Standalone CLI skill that drives isolated Playwright Chromium with Jev choosing scoped in-page actions, defaulting to Vercel AI Gateway with TypeSafe as an option.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
hqman/jev-browser-skillTypeScript
hqman/jev-browser-skillTypeScript47GitHub stars
Zero-dependency Node 22 adapter that puts typed Jev decisions beside any LLM, with swappable backends, confidence gates, MCP tools, an ACP sidecar, and offline-ready recipes.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
gamesonrblx/JevbridgeTypeScript
gamesonrblx/JevbridgeTypeScript22GitHub stars
Local browser-agent extension where FX plans tasks and Jev picks constrained actions from observed elements, with model calls routed through Vercel AI Gateway.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
razaanstha/ulkaTypeScript
razaanstha/ulkaTypeScript21GitHub stars
Pi guard plugin that checks inputs and tool calls with local rules plus Jev semantic judgements, with redaction and verification reminders.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
zszz3/Pi-Jev-GuideTypeScript
zszz3/Pi-Jev-GuideTypeScript2GitHub stars
Next.js spectator demo in which two independent Jev agents drive separate Snake browsers through same-origin iframes, clicking indexed direction buttons only, with each board state streamed to a server-only endpoint that returns the chosen target.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
raihankhan-rk/jevarenaTypeScript
raihankhan-rk/jevarenaTypeScript2GitHub stars
An agent tool and MCP call gate: paste a planned call plus its context and it returns allow, ask_human or deny with risk scores derived from a TypeSafe Jev decision call.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
ndolinschi/toolgateTypeScript
ndolinschi/toolgateTypeScriptFrom 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.