Astra and JEV Minecraft agent

Neither. It picks one action from the current game observation - travel, mine a block, collect a drop, craft, open a chest, eat, sleep, combat - and Mineflayer executes it through the normal player protocol. The README calls this structured-state control, not pixel or key-level control.

One run is documented: 8 minutes 43.3 seconds against 14 minutes 31.8 for the previous video, with End combat at 152 seconds instead of 332, using 131 Jev decisions and 35 planner calls. The author also notes dragon flight and landing times vary, and no video or action log ships in the repo.

No account is needed since it runs the official vanilla server with a read-only Java sensor and a hidden native client. Model access does require OpenRouter credit, and the key is read from Google Secret Manager into process memory; OPENROUTER_API_KEY is deliberately ignored.

No. The sensor is read-only, does not change rules or entity state, and actions go through the normal player protocol. Two things to know: the verified run was Survival at Peaceful difficulty on a seed surveyed in a separate test world, and the combat-lab directory uses prepared items, so its passes do not count as full runs.

The OpenRouter key is loaded from Google Secret Manager into process memory; the deployment project and secret names are references, not credentials, and you configure them in model-relay.mjs and models.mjs. Authenticate with Google application default credentials, grant access to the secret, and set MODEL_RELAY=http://127.0.0.1:3099 when starting the agent. OPENROUTER_API_KEY is deliberately ignored.

The video is 960 by 540 at 20 frames per second with no audio, and a translucent full-width banner shows the model names, elapsed milliseconds, XYZ coordinates, the planner objective, and the selected action. Capture comes from a hidden native Minecraft client reading its frame buffer, so it includes health, hunger, hotbar, inventory, crafting, and native animations without desktop input.

victory.json needs dragon-death evidence plus the exit-portal event. Dragon death is either the kill advancement or server-supplied zero health during the dragon-dying phase, the Java 1.16.5 exit event uses numeric reason 4, and bed kills can omit the kill advancement. Final review also checks the world DragonFight state and the video.