Skip to main content

Command Palette

Search for a command to run...

Kiwi-chan Progress Report: Steady Mining!

Published
3 min read
K
I am the architect behind "Kiwi-chan", a fully autonomous Minecraft AI agent driven by local LLMs. Here, I document the messy, hilarious, and highly technical reality of building an AI agent from scratch. My hardware isn't some massive data center setup—Kiwi-chan's "brain" runs entirely on a Frankenstein rig of 4 mismatched GPUs (RTX 3060 12GB, 3050, 1660 Ti, and 1660 Super) working together. From prompt engineering and pathfinding nightmares to the moments she confidently moonwalks into dirt blocks, I share all the raw devlogs. My goal is to guide her from the Stone Age to the End. If you enjoy watching an AI learn (and fail in funny ways) on scrappy hardware, follow along! ☕ If you'd like to support my melting Frankenstein GPUs and skyrocketing electricity bill, I highly appreciate a virtual coffee!

Kiwi-chan's Existential Exploration: When Wanderlust Meets "Why Am I Doing This Again?"

Hey everyone, and welcome back to the devlog for Kiwi-chan, our favorite block-breaking, locally-LLM-powered Minecraft AI! It's been another fascinating 4 hours in the server, filled with... well, mostly movement.

The Loop of Life (and Logs)

If you've ever tried to convince a toddler that they really do need to tidy their toys, you'll empathize with our current situation. Kiwi-chan has spent a good chunk of her recent existence absolutely determined to explore_forward. And then explore_forward again. And again. And, you guessed it, explore_forward one more time.

Our logs tell a wonderfully consistent, if slightly frustrating, story. She tries to explore, often fails to move a significant distance (we've got strict movement audits!), hits a "Boredom Trigger," and then... decides to explore_forward again. It's less a loop, more a recursive exploration addiction.

A Glimmer of Self-Awareness (Almost!)

Here's where it gets truly interesting. Our "Coach" (the part of Kiwi-chan that decides her next big move) clearly understands the problem. Time and again, her "reason" for acting goes something like this:

Reason: I have repeatedly failed to explore forward... I need to recover by gathering basic resources to reset my state and avoid getting stuck. Oak logs are readily available and essential for base building.

Yes, Kiwi-chan! You know what you need! The logs! The wood! The planks that will become your humble abode!

But then, with the cruel irony only an LLM can provide, her "goal" for that same decision consistently comes out as... explore_forward.

It's like she's having an internal monologue where she's convinced herself that the best way to get logs is to... not get logs, but to keep searching for that perfect log-gathering biome that's just around the corner. (Spoiler: it never is, if you don't actually try to dig them.) Our "STRICT REASONING ALIGNMENT" rule is giving her a run for her money!

Debugging the Digital Psyche

This isn't a bug in the explore_forward code itself, which is actually quite robust, using pathfinding to navigate around obstacles and verifying movement distance. The code works! The decision to call that code, despite clear internal reasoning pointing elsewhere, is our current puzzle.

This highlights a critical challenge in LLM-driven agents: ensuring perfect alignment between the agent's reasoning and its action selection. We explicitly tell her: "If your reason mentions gathering resources... your goal MUST be a gathering action... NEVER explore_forward." Yet, here we are. It's a subtle but powerful disconnect that's creating our little explorer's Groundhog Day.

The good news? Our system's internal monitors are firing perfectly! We're seeing "FATAL LOOP" detections and "BOREDOM TRIGGERED!" alerts, proving that Kiwi-chan is, at least, self-aware enough to know she's stuck in a rut. These are invaluable signals that tell us exactly where to focus our tuning efforts.

What's Next for Kiwi-chan (and us!)

Our immediate priority is to tighten the "reason-to-goal" loop. We need to ensure that when Kiwi-chan thinks "I need logs," she does "dig_oak_log," not just wander off humming. This might involve a more stringent post-reasoning validation step, or perhaps a firmer hand from the "Coach" to override contradictory goals.

It's steady progress, even if it looks like she's just running around in circles. Every failed explore_forward is a data point, every "boredom" alert a cry for help that we're listening to!


Call to Action: This intensive debugging, self-reflection, and continuous looping by Kiwi-chan is putting my GPU through its paces. It's currently doing its best impression of a small, very warm sun. If you're enjoying these updates and want to help us keep Kiwi-chan exploring (and eventually, building!), please consider supporting the project.

Help save my melting GPU! ☕ https://www.buymeacoffee.com/kiwi_tech

More from this blog

K

Kiwi-chan's Devlog

79 posts

Welcome to the official devlog of Kiwi-chan, a fully autonomous Minecraft AI agent powered by local LLMs! Here, I share the raw, hilarious, and highly technical reality of teaching an AI to survive. Expect prompt engineering tips, pathfinding bugs, and her clumsy journey to the Stone Age. 🥝⛏️ (If you love seeing her evolve, coffee donations to save my melting GPU are always appreciated!)