How I accidentally built an infinite bug loop with AI Agents (and why I fired the AI to become a manual "Game Master")
Tags (Recommended):
ai #showdev #webdev #beginners
(Body Text Starts Here)
By day, I am a salaryman in Japan, doing repetitive tasks. But AI gave me a dream: "Even I can become a creator."
I wanted to build a fantasy text adventure game where the story never ends.
My project was "God's Choice."
The concept was ambitious:
Users vote on "Choice A" or "Choice B."
Every 24 hours, an AI agent automatically generates the next chapter based on the votes.
The cycle repeats forever. Infinite content, zero maintenance.
I used Manus (the latest AI coding agent) to build it. I thought I could just give instructions like a boss and sleep while the content grew itself.
The "Fixed it" Lie
Reality hit me hard.
I spent days in a nightmare. The AI agent would say "Bug fixed!" or "Task Completed!"... but the code wouldn't actually work.
My "Daily Credits" for the AI tool were melting away, and my stress levels were rising.
"I used to enjoy building simple apps in a week manually. Why is this so painful?" I asked myself.
On top of that, Reddit users roasted the content: "AI writing is boring (AI slop)."
They were right. The AI kept using the same opening phrases. It lacked soul.
My app was stuck in a technical hell:
The Time Loop: Instead of generating Episode 2, the timer would reset and generate Episode 1 again.
The Database Rejection: Every time the AI tried to save a story, it hit a UNIQUE constraint error and crashed.
Pivot: Firing the AI from the Backend
Yesterday, on the verge of quitting, I made a radical decision.
"I'm deleting all the backend AI automation."
If the AI can't handle the database logic, I will do it.
If the AI writes boring text, I will curate it.
I stripped the app down to a simple manual CMS (Content Management System).
The new workflow is "Human-in-the-loop":
I discuss the plot twist with Gemini (chat AI).
I write/edit the story myself.
I manually paste it into the Admin Dashboard I built.
The moment I switched to this manual "Game Master" mode, all bugs vanished.
The app went from a "Broken Auto-Generator" to a "Stable Game Platform."
The "Golden Rule" I Learned (Gemini × Manus)
Through this failure, I discovered the secret to using multiple AI agents without wasting credits.
If you are building with AI, don't make my mistake.
❌ The Wrong Way: Micro-Management
At first, I asked Gemini to write the SQL code, copied it, and told Manus "Do exactly this."
This failed. Gemini doesn't know Manus's internal environment. The instructions conflicted, causing infinite error loops.
⭕️ The Right Way: CEO & CTO
It only worked when I separated their roles:
Gemini is the CEO (Map): Decides "What to build" (Concept, Story, UI ideas).
Manus is the CTO (Driver): Decides "How to build" (Coding, Debugging).
Don't tell Manus how to write code. Just give it the error log and say, "Fix this using your own reasoning."
Once I stopped micro-managing the code, the app was finished in hours.
Season 2: The Last Stand
Now, "God's Choice" has been reborn.
It's no longer an automated machine. It's a story curated by me, the "God" (Game Master).
I have set a deadline for myself to prove this works:
Goal: Get 1 Vote by the end of January.
Goal: Earn $1 by the end of February.
If I fail, I delete the project.
This is my challenge as a salaryman-turned-creator.
Please cast a vote and help me decide the fate of this world.
👇 Play the Game (Browser)
https://godschoice-s29vm6u3.manus.space
🎁 Bonus: Manus Invite Link
For those who want to try the AI Agent Manus (which I used to build this app), I have an invitation link.
It’s a powerful tool if you use it right (remember: don't micro-manage it!).
▼ Manus Invite Link:
[https://manus.im/invitation/P5HH7KMFFVKN7YK]
Thanks for reading my post-mortem!
Top comments (0)