HunterAlphaHub
OpenRouter model reference Facts from the public catalogue, dated and labelled
Jev Laya Fable 5.2 Verified
2026-11-13

GitHub · Games and real time · Research and data

rmalde/minecraft-agent

End-to-end times for a Jev loop, which almost nobody publishes.

The repository's GitHub card, read on 2026-09-23

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

Stars
558
Forks
56
Language
JavaScript
Last push
2026-09-20

Read from the GitHub API on 2026-09-27. 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.

Open the repository ↗All builds

Send us a link

A project built with Jev, a post, a video, a correction, a tip. We open the link, check it says what you said it says, and write the entry ourselves.

Required a link, and an email to reply to. Optional everything else.

Add context — all optional

One or two sentences about what it does, in your words. We write the entry ourselves.

Cost, latency, a benchmark — anything you measured. We attribute these to you.

We store what you type and email it to ourselves. No IP address, no user agent, no referrer — the same rule as the mailing list.

What happens to what you send →