
Sign up to save your podcasts
Or


Four hours of Forge Island development, 04:05 to 08:05 HST on September 21, 2026. A machine restart killed the worker fleet, the design was rewritten to run one card at a time, and thousands of lines of orchestration were deleted. The hosts walk through the lead session and its helper crews, the two hourly routines that now look after the pipeline, why a worker’s say-so no longer counts as verification, and what still has no owner.
Published 2026-09-21 (UTC). Source notebook: AI Bots Deleting 19000 Lines of Code
NotebookLM deep dive: 796c23cb2285060c1c0b774663e694eeae0ee13925157647bf814027705a6367
Eight hours of Forge Island development, from 3am to 11am Hawaii time, weighted toward the last hour.
The subject is the orchestration itself: how a fleet of bots builds an Unreal game on one machine, what worked, what broke, and what changed because of it.
This progress report details development logs for Forge Island, specifically focusing on the status of several task cards involving Unreal Engine integration. Work on features like the phone microphone relay, ambient life animations, and guided assistant tours has stalled due to persistent technical hurdles. System errors, specifically Windows process failures and read-only filesystem restrictions, have repeatedly blocked workers from executing necessary commands. Additionally, several tasks are currently sidelined because they require access to a global build lock held by other processes or need manual intervention to repair broken dependencies. While some assets and visibility fixes have been successfully merged, final visual proof for most features remains unfinished. Development is further complicated by a specific ruling requiring human voice recordings instead of synthetic audio for certain validation steps.
Published 2026-09-20 (UTC). Source notebook: Why Forge Island AI built nothing
NotebookLM deep dive: 21b77ba1e230425d9aceb8c72ef09ced6a9531dc02bfca7f85e97e2881d3ffd5
A laser pointer sounds like a ten-minute job. It took five hours.
This episode follows the whole detour: what the agent fleet thought it was building, where the work disappeared into its own process, and how a trivial feature turned into an afternoon. The interesting part is not the laser pointer. It is watching an automated team trip over the rules it wrote for itself.
From the Forge Island devlog, where a game is being built almost entirely by AI agents.
These progress logs detail the development of Forge Island, focusing on the integration of Unreal Engine systems with web-based infrastructure. A major highlight is the implementation of a remote microphone relay that allows mobile phones to function as voice controllers for an in-game drone. The documentation also covers a comprehensive communications check verifying connectivity with external tools like T3 Code, Codex, and Slack. Developers addressed various gameplay enhancements, including ambient life animations for a crop duster, refined tractor spawning logic, and automated "window guard" protections for user sessions. Technical hurdles involve managing build lock sequencing, resolving C++ compilation errors, and ensuring asset parity across multiple developer worktrees. Final status updates emphasize the use of automated testing and visual captures to validate features like Tobii eye tracking and revamped audio settings.
Published 2026-09-20 (UTC). Source notebook: Why AI agents built a glass dome
NotebookLM deep dive: 4c3e15ef099250f5b11de50151c6e9f27c5f59ac0ffe062278075701c429efaf
From the publisher's feed
Forge Island is a game being built almost entirely by AI agents. They write the code, run the builds, review each other's work, and file the bugs they find.
Every few hours a fresh account of…
If you want to know what it actually looks like when software is written by a fleet of agents instead of a team of people, this is the log.