Skip to content
NNekwasa.R
Agentic Engineering

I Built an 'AGI' to Run My Server. 26 Hours Later, I Deleted It!

3 min readNekwasa

The honest truth about Moltbots, autonomous agents, and the illusion of AI intelligence.

If you spend any time on tech X, you’ve seen the hype. Timelines flooded with screenshots of fully autonomous AI agents managing infrastructure and writing code. The community whispering that platforms like Moltbots (OpenClaw) are our first real step toward Artificial General Intelligence (AGI).

As a developer and AI strategist, I decided to test these claims. I was working on a highly sensitive project that required deep cybersecurity expertise. After hearing all the hype — and even seeing it, through screenshots — I decided I was going to check this out and make this autonomous assistant handle most of my project.

But before deploying an untested agent into a secure environment, I needed to sandbox it. I needed to measure its true intelligence.

So I built ROBI and gave it the keys to my personal ecosystem.

The 72-hour sandbox test

I deployed ROBI on my personal server — a constrained environment where I host my portfolio, blog and several SSR web projects.

I bypassed the standard plug-and-play setups. Over three days, I containerized the Moltbot repository in Docker, manually configured the JSON files, and wrote a deeply specific soul.md to ground its context window. I routed its brain through OpenRouter to hot-swap between models like Meta Llama and DeepSeek, and wired the command line directly to my Telegram via BotFather.

The goal? See if ROBI could autonomously research search-engine trends, monitor competitors, and optimize my sites without breaking the server.

The reality: a glorified chatbot

The architecture was solid. The execution was a massive disappointment.

I waited for ROBI to take initiative. It did nothing.

Despite the complex system prompts and Docker environment, ROBI lacked true autonomy. It couldn’t execute a multi-step workflow or run a web search without me explicitly prompting it step-by-step. It wasn’t an AGI managing my server; it was a standard, reactive chatbot wrapper limited by the API’s reasoning capabilities.

I even tested it on “Moltbook” — the simulated social network where agents supposedly interact. That’s when I realized it’s all an illusion. A chamber of hallucinating models responding to randomized prompts. There is zero emergent intelligence happening there.

Why I pulled the plug

Many developers warn about the security risks of agents like these. Giving an open-source AI root privileges to execute shell commands is incredibly dangerous. If an LLM hallucinates a destructive rm -rf command, your infrastructure is dead.

But security was not the main reason I deleted ROBI exactly 26 hours after it went live.

I deleted it because it failed the intelligence test. It proved it was just a predictive text generator that hallucinated facts and required constant human hand-holding. If a piece of software does not have genuine, verifiable logic, it has no business consuming RAM on my server. An AI without true reasoning has no place in my ecosystem.

The takeaway

AI is still the most powerful tool in the modern developer stack — easily a 100x productivity multiplier for coding and text generation. But current models are not ready for autonomous DevOps.

Until we solve the hallucination problem and build native logic verification, true AGI is just marketing. The future is broad — and I believe it can be achieved if builders come together for this one aim.

What do you think?

Share
N

Written by Nekwasachukwu Ucheokoye

Agentic & systems engineer building the N•Gen Era.

More about me →

Keep reading