GitHub · Research and data
rmalde/minecraft-agent
End-to-end times for a Jev loop, which almost nobody publishes.
What it does
An agent that plays Minecraft 1.16.5 with a planner choosing goals (GPT-6 Astra or GPT-5.6 Sol) and Jev choosing the player's actions, published with the runs: the latest verified one, nether-final-08, completed in 8 minutes 43.300 seconds, against 14 minutes for the previous recording.
The repository's own description: “Astra planner and JEV controller for Minecraft, with native recording, tested routes, and run verification.”
How it works
A vanilla server plus Mineflayer for input, a read-only Java sensor that can report the exact dragon head position, and a separate native client and observer; each chosen action goes to the game through the normal player protocol, and the README states it does not change game rules or entity state.
The repository, by the numbers
Read from the GitHub API on 2026-09-22. Stars and the last push move daily — quote them with the date, the way we do.
Numbers the author reports
These are the project's own figures, not our measurements — we keep ours on the statistics page and label them as ours. Read on 2026-09-23, with the sentence each figure appeared in:
- 8 min 43 sone Nether run, start to finish
- “The latest run, nether-final-08, completed in 8 minutes 43.300 seconds.” — repository README
What we checked
- the tree: native-client, observer, combat-lab, optimization, research (69 entries)
- no LICENSE file at the root
- README's latest verified run time and the previous recording's time
- README states the sensor is read-only and that game rules and entity state are not modified
What we did not check. We did not run it; the run time is the author's recording, not a measurement we made.