brobot.Download ↓
BroBot Core 0.2 · Local command parsing, action execution and bounded starter survival. Optional API-powered planning is configured separately.
BroBot / Features

A useful little
plus one.

See what BroBot can do, how you control it and where its experimental modes fit.

01 / A SECOND PAIR OF HANDS

Your world.
With a plus one.

Not another menu to manage. A companion you can direct, inspect and stop whenever you need.

♟♟♟
GATHER

Leave the legwork
to your little guy.

Mine reachable blocks and collect actual drops. BroBot checks what made it into its inventory, not just what broke.

→
⛏
CRAFT

From “need wood”
to “made it.”

Turn carried materials into tools, use furnaces and build simple structures. Real ingredients. Verified outputs.

EXPLORE

Keep up.
Find the way back.

Follow visible players, navigate to coordinates and return to remembered places. Unsafe or exhausted plans pause.

02 / A SMALL COMMAND. A REAL PLAN.

Tell it where
to start.

Try an illustrated command walkthrough. This demo explains the flow; it isn’t connected to a live Minecraft world.

Direct commands and the experimental starter need no API key. Natural-language planning is optional and uses separately billed OpenAI API calls.

BROBOT / COMMAND WALKTHROUGH DEMO

❯ survive starter

PICK YOUR APPROACH

Three ways
to team up.

01 / DIRECT

You call the shots.

Use explicit commands for navigation, gathering, crafting and other bounded actions. No API key required.

follow me
02 / OFFLINE STARTER

One goal. Many steps.

A deterministic controller observes the world and chooses the next action for a starter kit and return. Experimental, with explicit limits.

survive starter
03 / OPTIONAL PLANNER

Put it into words.

Use the OpenAI API for written goals and bounded tool selection. API billing is separate. Live model behavior remains untested here.

goal Gather nearby logs
RECOVERY UPDATE

A little more room.
A checked way home.

The pickup controller can now consider one visible block removal that creates safe standing space beside tracked materials. It verifies dry support and both walking directions before normal mining rechecks the real world. The separate experimental action descend_notch {} lowers the bot through one adjacent leaf; it does not automatically solve a whole treetop descent.

EXPANDED EXPLORATION

More ground.
A checked route back.

Starter jobs can now search within 256 blocks of home, with up to 24 scouting trips. Each trip stays locally bounded, and long returns use observed waypoints with checked walking routes. Wider range does not guarantee full coverage or success.

CORE 0.2 / WHAT CHANGED

Small decisions.
Better habits.

Five concrete improvements to how the starter gathers, crafts and finds its way. Core is BroBot’s software release, not a newly trained foundation model.

01

Keep a way out.

Before placing a crafting table, BroBot checks for a walking exit and a route back. If a spot would trap it, it tries another.

View the change
02

See across chunk corners.

Nearby resource searches now cover diagonal chunk sections while keeping the same collection radius and movement checks.

View the change
03

Try a different approach.

A failed short route or a trip back over familiar ground no longer stays in the fallback list forever. BroBot tries other bounded choices.

View the change
04

Skip the needless rechecking.

Tree scans run when wood is needed. After a failed scout, unchanged surroundings can lead straight to another search instead of repeating the same mining attempts.

View the change
05

Switch priorities when it matters.

Once the pickaxe and furnace are in its inventory, returning takes priority over old gathering plans. Urgent eating takes priority too. A safe route still has to be found.

View the change

Still a development build. Canopy escapes, difficult terrain and long returns can fail. See every recorded outcome before deciding whether it fits your world.

SINCE CORE 0.2 · IN DEVELOPMENT SOURCE

Fewer repeated searches.
Clearer recovery.

The October 8 fix keeps a verified empty search valid through an unrelated distant terrain update, so a stationary failed scout can move on to another scout. Movement, nearby changes, hazards and fresh materials still trigger rechecking.

This changes retry scheduling; it does not grant permission to mine or guarantee a successful route. The selected difficult world still failed its step budget.

See the current source and evidence →