Doom flown as a spacecraft payload: a ground-side jev pilot picks where to go every half second while F´ flight software, CCSDS frames, Yamcs and Open MCT carry the telemetry and video down.
Organization repository on GitHub
F´ flight software → CCSDS/Yamcs → Open MCT, with jev (System One) and Claude Sonnet 5 (System Two) driving Doom over that real mission stack.
Repo stats from the GitHub API, cached Oct 2026.
Doom runs as the payload of a spacecraft. An F´ flight computer sends its telemetry and video down through CCSDS frames to Yamcs, and you watch it in Open MCT or a small dashboard. The pilot on the ground is jev (TypeSafe's fast decision model). Every half second it picks where to go and uplinks an intent. Claude reviews each attempt. No part of the pilot ever reads the level file. On 24 September 2026 jev finished E1M1 in 105 s, with no deaths, through the full stack.
Quoted from the project's README. Read the full README.
Watch out
Supported end to end on Linux and WSL2; the README says nobody has run the macOS path yet and names the bundled Java runtime and ViZDoom wheels as the likely failures. Install takes roughly 3 GB of disk and 15 to 20 minutes, and a TypeSafe API key is required for jev, while Claude reuses your Claude Code login. The headline level finish is one run on one machine with link round-trip latency in the loop, so read it as proof the stack works rather than a capability benchmark. Everything on screen arrives as telemetry, which also means the picture lags your inputs. Copy reviewed against the repository README on 2026-10-04, not from running it.
TypeLLM/TypeLLMPython
fidecastro/jevifyPython
zwliJay/jev-forgePython
jonathanavis96/jev-kitPython
bladedevoff/stuntdPythonOriginal write-ups on what this entry is for.
Posts from builders shipping with Jev right now.
