Download jevry.
Unsigned developer packages for macOS and Windows. They install, they run, and they will be replaced by signed builds once signing and notarisation are in place — so treat these as builds for trying, not builds for trust.
Packages
Sizes and digests are read from the files themselves at build time. Verify the digest before you unpack anything.
macOS 12 or newer · Apple silicon
Disk image. Unsigned developer build — macOS will ask you to confirm the first launch.
SHA-256 4a0bf04e109b3423e10a20d066555a62ab0cda29f476c486f91230235ff8da49
macOS 12 or newer · Intel
Disk image for Intel Macs. Same build, same unsigned status.
SHA-256 9296152059e27fe0dd770b966ffd961ca17f80a26afd3803f3d76d0a63939ce5
Windows 10 or newer · x64
Installer. Unsigned developer build — SmartScreen will warn until signing lands.
SHA-256 f1ebafaf3d3dc78cf166c41167234b1a914acd6d5b943d7b99e89223459505fd
Check every file at once:
shasum -a 256 -c checksums.txtchecksums.txt lists all packages — 3 files.
What is inside
Four things have to exist before a task can run. Three of them are yours.
Node.js
22.12 or newer, with npm
Jev model key
A TypeSafe API key — the System One endpoint, not Chat Completions
Text model
A locally authenticated Codex or Claude Code CLI, or your own API provider
Vision
A provider/model that accepts images, for games and other visual flows
Updating
These builds have no auto-updater. Keep the package you downloaded: the digest on this page is the record of what you installed, and it is how you tell whether a later build is the one you meant to run.
Coming next: signed installers, notarisation and an update channel — the first item on the roadmap.
The recorded run shipped with this build
The 2048 replay on the home page is generated from a run recorded locally: 1333 moves, final score 25,800, maximum tile 2048. The page re-simulates it from the seed and the move list, so what you watch is the game that was played.