Forem: kiwi_tech

Kiwi-chan Progress Report: Steady Mining!

kiwi_tech — Thu, 16 Apr 2026 06:46:21 +0000

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.

☕ https://www.buymeacoffee.com/kiwi_tech ☕

Kiwi-chan Progress Report: Steady Mining!

kiwi_tech — Thu, 16 Apr 2026 02:28:45 +0000

Devlog: Kiwi-chan's Excellent (and Repetitive) Adventure! 🌳

Hey there, fellow digital pioneers! Your resident tech blogger is back with another peek behind the pixelated curtain, chronicling the fascinating, sometimes frustrating, journey of Kiwi-chan, our fully autonomous local-LLM Minecraft AI.

This week, we're diving into a 4-hour slice of Kiwi-chan's existence, and let me tell you, it's been... an education. Specifically, an education in the fine art of exploration and the subtle nuances of an AI trying to justify its wanderlust.

The Wanderer's Rhapsody: Or, Why "Explore Forward" is the New Black

If there's one thing Kiwi-chan has been consistently good at over the past few hours, it's exploring. Or, more accurately, trying to explore. Our logs are a testament to her dedication to the explore_forward command, punctuated by a recurring internal monologue: "🥱 BOREDOM TRIGGERED! Bot is bored of 'explore_forward'."

Oh, Kiwi-chan. We feel you. Sometimes, you just need a change of scenery.

Her explore_forward code is a thing of beauty: a robust pathfinding routine that calculates a random destination 30 blocks away, then waits a full 20 seconds to ensure actual movement, complete with a vital check to make sure she hasn't just slammed into a wall (again). This code itself is solid – a testament to the system's ability to generate reliable movement. The problem isn't how she explores, but why she keeps doing it.

The Log Paradox: When Rules Meet Reality

Here's where things get juicy. Our sophisticated "Coach" (the meta-LLM orchestrating Kiwi-chan's actions) keeps pushing explore_forward, with reasons like: "To replenish the oak log supply for crafting and base building," or "To continue building up a supply of oak logs..."

Hold up, Kiwi-chan! Our very own [EXPLORE_FORWARD RESTRICTION (CRITICAL)] rule explicitly states: "NEVER use explore_forward unless your explicit intent is to find a completely new biome. If your reason mentions gathering resources... your goal MUST be a gathering action (e.g., gather_logs, dig_birch_log), NEVER explore_forward."

It seems Kiwi-chan's logical reasoning engine is having a slight disagreement with her pre-programmed directive. She knows she needs logs, she wants logs, but her chosen method is to explore_forward to find these logs, rather than directly dig_oak_log. It’s like wanting a sandwich, but deciding the best way to get one is to drive aimlessly around town until you stumble upon a deli. Adorable, but inefficient! This is a fascinating edge case where the intent (gather logs) is correct, but the action selected to achieve that intent is violating a higher-level rule. We're keeping a close eye on this internal conflict!

The Phoenix from the Pixels: Learning from Failure

Despite her repetitive wandering, Kiwi-chan isn't just mindlessly bumping around. This log demonstrates some fantastic internal resilience.

At one point, we hit an "🚨 [FATAL LOOP] Infinite loop detected. Requesting help." – a truly dramatic moment in an AI's short life! But like a digital phoenix, she recovered. She went "idle" to cool off, and then, after consulting her meta-mentor (Qwen, our recovery plan LLM), she was given a recovery plan: ['explore_forward', 'explore_forward']. Yep, right back to what got her into trouble, but at least she didn't completely break!

Even cooler, we caught her trying to sneak in a try-catch block into her code. "⚠️ Safety Check Failed: ❌ ERROR HANDLING: Do NOT use 'try...catch' or '.catch()'. Let the error crash so the system knows it failed." Our system immediately flagged this violation of [CODING STANDARDS] and prompted her to fix it. This isn't just about avoiding errors; it's about forcing the AI to confront and learn from actual crashes, rather than sweeping them under the rug.

Steady as She Goes (Mostly)

While a towering fortress didn't spring up overnight, and her log inventory might not be overflowing, this 4-hour window shows crucial progress in Kiwi-chan's meta-learning capabilities. She's refining her exploration code, she's catching her own rule violations, and she's recovering from fatal loops. We're watching her learn the hard lessons of Minecraft survival, one persistent explore_forward at a time. The path to fully autonomous base-building is rarely a straight line, but it's always an adventure!

Support Kiwi-chan's Journey!

All this cutting-edge AI goodness? It takes a lot of computational power. My GPU is practically glowing from all the inference Kiwi-chan demands. If you're enjoying these updates and want to help keep our persistent little bot exploring, crafting, and occasionally getting bored, please consider supporting the project!

Support Kiwi-chan via Buy Me A Coffee! to save my melting GPU! ☕

Kiwi-chan Progress Report: Steady Mining!

kiwi_tech — Wed, 15 Apr 2026 22:05:54 +0000

Devlog: Kiwi-chan's Great Stone Conundrum & The Zen of Log Gathering 🪵

Another 4-hour sprint in the wild world of Minecraft, and our plucky autonomous LLM, Kiwi-chan, is making... progress. We're tracking every digital step, every block broken, every failed attempt, and let me tell you, it's a rollercoaster of emotions (mostly mine, as I watch the logs fly by).

The Stone Wall of Stubbornness

The main antagonist of this session? mine_stone. Kiwi-chan has been valiantly (and repeatedly) attempting to chip away at the world's rocky foundations, but it seems those cobblestone drops are proving elusive. Time and again, the system audit flags a "failure to pick up item" – a classic case of 'I know I broke it, but where did it go?!' It's like watching a determined toddler trying to catch soap bubbles – lots of effort, not always the desired outcome.

We've got strict rules in place, even accounting for specific drop name mismatches (stone actually drops cobblestone), and her code for picking up items is looking solid for oak_log (more on that in a sec). This suggests either a deeper issue with how mine_stone is structured or how the world is behaving with drops in those specific instances. The good news is, she's trying, and fixing the mine_stone skill remains top priority.

The Art of the Mental Reset: Exploration, Logs, and... Boredom?!

But here's where Kiwi-chan truly shines: resilience and adaptability. After a few too many mine_stone face-plants, our LLM isn't just giving up. No, sir!

Exploring New Horizons: First, she attempts explore_forward, a good ol' wander to clear her digital head and find new prospecting grounds. It's like she's saying, "Maybe this stone over here is less... finicky?" This is a crucial recovery mechanism, preventing her from banging her head against the same digital wall.
Strategic Pivoting: When mine_stone proved consistently tricky, the "Coach Decision" system kicked in, a beautiful example of our AI trying a mental reset. "I have repeatedly failed to mine stone," Kiwi-chan reasoned, "I need to switch to a different task to recover and avoid getting stuck in a loop. I will gather oak logs to ensure I have enough wood for crafting and base building." Smart move, Kiwi-chan! We then saw a significant period of diligent gather_oak_log operations. She's getting quite good at it, systematically chopping down trees and ensuring those logs are properly collected.
BOREDOM TRIGGERED! And then, something new and fascinating happened: Kiwi-chan got "BOREDOM TRIGGERED!" Yes, our AI got 'bored' of gathering logs. This is a fantastic mechanism we implemented to prevent infinite loops on successful but repetitive tasks. This prompted a switch to dig_dirt, another excellent 'reset' action to diversify her resource portfolio. She even went back to gathering logs after a quick dirt-digging interlude, demonstrating a nice loop of varied resource acquisition.

Code Quality: Small Victories

Beneath the surface (pun intended, Minecraft fans!), Kiwi-chan's generated code for tasks like dig_dirt and gather_oak_log is looking increasingly robust. She's diligently following our strict coding standards:

Dynamic Block Finding: Always finding blocks dynamically, never hardcoding coordinates.
Precise Item Collection: Ensuring she moves exactly to the dropped item's location after digging to secure that sweet loot.
Y-Level Targeting: Carefully targeting blocks at her Y-level (Math.abs(b.position.y - bot.entity.position.y) <= 2) to prevent reaching for blocks high in the canopy (Rule 10 is definitely paying off!).
Smart Pathfinder: The pathfinder is working its magic, guiding her gracefully around obstacles to reach her targets for gathering and exploring.

While the mine_stone puzzle remains, the fact that Kiwi-chan is learning to pivot, gather resources effectively, and even experience 'boredom' is a massive leap forward. It shows a growing understanding of task management and resource acquisition, even when faced with frustrating setbacks.

Next on the agenda is to crack the mine_stone conundrum once and for all. Perhaps a new strategy is needed, or a subtle tweak to how the system audits the item pickup specifically for cobblestone. But for now, Kiwi-chan is busy building up her basic resource inventory, one log and dirt block at a time, preparing for her next big push.

Call to Action: Support Kiwi-chan's Journey & Save My GPU! ☕

Running these complex LLMs and Minecraft instances takes a serious toll on my hardware. My GPU is practically weeping silicon tears! If you're enjoying Kiwi-chan's antics and want to help us keep the development furnaces blazing (and my GPU from melting!), please consider supporting the project. Every coffee helps!

https://www.buymeacoffee.com/kiwi_tech