User repository on GitHub
Chess where both players are TypeSafe's Jev model: every move is a typed Choice decision
- Forks
- 3
- Last pushed
- Updated Sep 2026
Repo stats from the GitHub API, cached Oct 2026.
Two Jev players playing chess with no engine: code owns the rules and the tactical facts, and the model returns one Choice per legal move with a probability for each, plus a Score for the position and a Noul for sharpness.
User repository on GitHub
Chess where both players are TypeSafe's Jev model: every move is a typed Choice decision
Repo stats from the GitHub API, cached Oct 2026.
This is one of several Jev listings for the same project. The canonical entry is TypeSafe Chess — Dimesio.
Two virtual chess players, both powered by TypeSafe's System One model Jev. No engine, no generated text: each move is a typed decision that the model returns with a full probability distribution, and the code does the rest. Optionally, a Monte Carlo Tree Search uses those same distributions as policy and value, AlphaZero-style, to play noticeably better.
Quoted from the project's README. Read the full README.
Watch out
Cost is the first thing to check, because the two modes differ by an order of magnitude: a fast move is roughly 2-3k tokens and about 350 ms end to end, while an MCTS move with 16 evaluations runs around 40-50k tokens and 3 seconds, and a single MCTS game reaches about 2M tokens. Strength numbers carry a stated caveat - the elo ladder plays a lite WASM Stockfish at fixed depth, so the figures are relative rather than FIDE, and eight games give roughly plus or minus 200 Elo. On the measured side, the regret script scores the fast move and the MCTS move on identical positions and reports centipawn loss: the sweep table puts fast mode at 168-190 cp average loss and the best MCTS configuration at 25 cp, over two rounds of 20 tactical positions at oracle depth 12 with 16 evaluations. Worth knowing that the first MCTS version lost to the single-call player, because Jev's Score is an absolute judgment that calls every child position clearly better once one side is materially ahead, leaving the tree nothing to rank on; the fixes are code-side tactical facts. The README continues past the point this listing's source text ends, cut off inside the tuning-loop discussion. Copy reviewed against the repository README on 2026-10-04, not from running it.
Original write-ups on what this entry is for.
Posts from builders shipping with Jev right now.