Birth of BabyAGI
AI Summary
Nakajima's first-person account of how a weekend hack became the ancestor of every task-loop agent. BabyAGI stored task/result pairs as embeddings in Pinecone and used them as crude long-term memory, feeding past outcomes back into task generation. The architecture is naive by 2026 standards, but its influence is outsized: the three-agent loop (execute, create, prioritize) showed up later in Letta's agent server, in LangGraph's state machines, and in Park's generative agents. Worth reading for how early this stack felt figured out, and how much was missing.
Original excerpt
Fascinated by the #HustleGPT movement, where people are using ChatGPT as their cofounder, I asked myself if we could build an “AI founder” that could run a company autonomously. I came up with a base architecture, which I described to ChatGPT and started building. About 50 prompts later, I sharedthis working prototype.
Interestingly, I found that you could provide any objective (not just to start a company). You can see it researching various ways to make the world a better placehere.
The response was wild. It started with one friend calling it AGI, then another calling it Skynet, then the AI doomers found it. I jokingly asked the autonomous agent tocreate as many paperclips as possible–…
18 more articles in this vault.
Import the full Agent Memory Patterns vault to Burn 451 and build your own knowledge base.
Content attributed to the original author (Yohei Nakajima). Burn 451 curates publicly available writing as a reading index. For removal requests, contact @hawking520.