Jev case: Yesterday, GLiNER2.5 played doom.

@tazr_dev Trent Zock-Robbins · Sep 18, 2026 · case #925822 · listed via Jev Hub

Still from the clip posted with this case; watch it in the original post on X.

Kept GLiNER2.5's embedder and trained a small decision head on its output to make a homebrew decider model.

The original post

Yesterday, GLiNER2.5 played doom. Rapid play looks coherent, but Jev has a secret sauce: decisions. So, I kept the embedder and trained a small decision head on the output. Now it's a homebrew decider model on embeddings. What homebrew decider model will you make this weekend?

Engagement when collected

Likes3

Bookmarks0

Reposts0

Replies0

Quotes0

Numbers are a snapshot taken from X when the case was added to the library (schema v1, collected 2026-09-19); they will not match today.

Where this case fits

Filed under coding & developer tools, games & playable demos. In the pattern Jev is built for, the model answers a bounded question per step — and ordinary code acts on the answer, because the answer is already a value rather than a paragraph. Other posts in the same family are on the coding & developer tools page.

🛠️ Coding & developer tools 🎮 Games & playable demos