minecraft-jev-agent
Embodied Minecraft agent where a typed decision plane (Jev or Liquid d1) picks grounded transitions and a kernel owns verification.
Overview
minecraft-jev-agent is an embodied Minecraft Java agent with a strictly layered architecture, declared permanently locked as version 4.1.2. A sparse LLM planner synthesises what to do; a Typed Decision Plane, a System One model such as Jev or Liquid d1 selected by profile, decides which grounded, enabled transition to take and whether to take it; a kernel owns lifecycle, leases, effects, trusted facts and the sole authority to declare success; and Mineflayer is the motor layer behind a runtime adapter. Layers are separated by how far ahead they reason, not by tick rate.
The production path runs from a proposal to a typed kernel command, through admission and resource leases, a persistent transition controller and the adapter, with a VERIFY step over fresh facts as the only success authority (true, false or unknown) before re-deriving the frontier. A viability runtime can suspend and resume without silently replacing mission intent. It uses stock Mineflayer plus one reversible local patch, runs on Bun only, and the README notes 'Jev' in identifiers is a historical name for the decision plane.
What the decision model decides
| Type | Question | Answers |
|---|---|---|
| Choice | Which grounded, enabled transition should the agent take next? | — |
| Yes / no | Should this transition be taken now (whether)? | — |
How it works
- Sensors build a verified world model
- Enabled transitions are grounded
- Typed Decision Plane chooses which and whether
- Kernel admits with leases; controller realises the transition
- VERIFY over fresh facts decides success; frontier is re-derived
Strengths
- Model only chooses among grounded options
- Kernel and VERIFY keep authority over success
- Pluggable decision model
Caveats
- Complex architecture
- Bun-only
- Architecture explicitly frozen
At a glance
- Type
- Project
- Status
- research
- Language
- TypeScript
- Runtime
- Bun with Mineflayer
- Has code
- yes
Use cases and integrations
How curated lists describe it
Embodied Minecraft Java agent: a Typed Decision Plane (Jev / Liquid d1) chooses among grounded transitions, a V4.1.2 kernel owns authority, leases and VERIFY, and Mineflayer is the motor layer. Bun-only.
hellogumbo/awesome-jev
Frequently asked questions
What does the decision model decide?
Which grounded, enabled transition to take and whether to take it.
Who decides success?
Only the VERIFY step over fresh facts, owned by the kernel.
Must I use Jev?
No, the decision plane can be Jev or Liquid d1.
Related projects
Craftax survival agent where Jev picks one Choice per step from code-listed actions, with optional LLM goals, plus ablations.
ProjectresearchPythonMineflayer Minecraft bot where code lists feasible actions and Jev picks one in about 0.2 s; 15 of 40 runs reached the Nether.
ProjectresearchTypeScriptAn LLM writes a task-specific Jev harness, improved with rewards and traces; a Pokemon harness rose from 25% to 75% wins.
ProjectresearchPythonBenchmark where Jev steers an agent through 100 key-and-door grid puzzles, one Choice per move, scored against an exact BFS solver.
CLIresearchPythonSource for browser chess and Chess960 where code computes each legal move's facts and Jev picks one per turn as a typed Choice.
ProjectproductionTypeScriptBrowser 1v1 sniper arena where Jev reads match state about 9 times a second and chooses movement, aim, ADS, firing and jumping.
ServicebetaTypeScript