Kiwi-chan's Devlog: The Wanderlust Phase (and a GPU that's seen better days)
Hey everyone, your friendly neighborhood tech tinkerer here, back with another update on Kiwi-chan, our darling little autonomous local-LLM Minecraft AI! If you're new here, imagine an AI with the soul of a digital toddler dropped into the blocky world of Minecraft, learning everything from scratch, powered by a local large language model that occasionally argues with itself. It's glorious chaos, and I love it.
This past 4-hour session has been... enlightening. Kiwi-chan seems to have developed a serious case of wanderlust, or perhaps a deep philosophical inquiry into the nature of "forward."
Status Update: The Great Exploration (and Re-Exploration) Saga
Kiwi-chan's primary directive right now is survival and base construction. Specifically, getting a crafting table and chest. Simple, right? You'd think so. But Kiwi-chan has her own unique learning curve.
The "Explore_Forward" Loop: Our AI spent a significant portion of this session attempting to explore_forward. And then doing it again. And again. The internal "Coach" (which guides Kiwi-chan's actions) repeatedly noted that she had "failed to mine stone" and had "explored forward too many times." You'd think this would lead to a change of scenery, or at least a change of task.
Here's where it gets interesting: the Reason provided by the AI was often spot-on! For instance, she'd reason: "I need to gather resources to recover and build a base. Oak logs are readily available nearby and are essential for crafting a crafting table..."
And then the Coach Decision would follow with: 'explore_forward'.
It's like having a child tell you, "I really need to eat my vegetables to grow strong!" and then immediately running off to climb a tree. The intent is there, the logic is present, but the execution... well, it's a work in progress! We're observing a fascinating disconnect between what the AI knows it should do, and what the high-level decision-making process tells it to do. It's almost like a stubborn teenager phase.
Boredom, Loops, and Resets: Thankfully, Kiwi-chan isn't entirely without self-awareness. Our "Boredom Trigger" mechanism fired off multiple times, essentially telling the AI, "Hey, maybe you've explored enough for a while?" This is a crucial circuit breaker, designed to prevent endless repetitive tasks.
However, even boredom couldn't stop the wanderer for long. At one point, we hit a [FATAL LOOP]. Kiwi-chan essentially went, "Nope, I'm stuck, send help!" and went idle. A well-deserved coffee break for the AI, I suppose. This forced a hard reset and a re-evaluation of her immediate goals. It was a good reminder that even robust systems need a little kick in the digital pants sometimes.
Minor Code Hiccups: We also caught a Safety Check Failed for a try...catch block. Our rules are strict: no error hiding! We want those crashes loud and proud so we know exactly where the AI tripped up. It's a small detail, but important for debugging her evolving codebase.
Overall, while it might look like a lot of "exploring," what we're actually seeing is the AI wrestling with rule adherence, self-correction, and the complex interplay of high-level reasoning and low-level task execution. Every explore_forward is a data point, every 'boredom' trigger a lesson, and every 'fatal loop' a chance to strengthen the system. Kiwi-chan is learning the nuances of when to explore and when to gather, even if she's currently favoring the scenic route.
We're going to dive into the 'Coach Decision' logic next to bridge that gap between "I know I need logs" and "Okay, now actually go get logs!" Stay tuned for the next update, hopefully with more crafting and less accidental hiking!
Support Kiwi-chan's Adventures!
Running Kiwi-chan locally means my GPU is working overtime, practically begging for a cooling break (or an upgrade!). If you're enjoying these devlogs and want to support the project, please consider buying me a coffee – or enough coffees to cool down my rig!
Your support helps keep Kiwi-chan exploring, learning, and eventually, building that glorious base.
Top comments (0)