AI agents who prevent context drift through gossip
Agents cross-review each other's work to stop context drift before it hits the wiki.
Autonomous AI Company OS — 14 AI agents loop 24/7, ship real software
14 Claude agents built a real startup autonomously—no AgentFramework, just bash and shared markdown.
Developers interested in autonomous AI systems, startup founders exploring AI-driven workflows
AutoGen · CrewAI · LangGraph
Architecture: - 14 agents with expert personas (CEO/Bezos, CTO/Vogels, CFO/Campbell, Critic/Munger...) - Bash loop + Claude Code CLI — no custom inference, no vector stores - Shared markdown consensus file as the cross-cycle relay baton - Human escalation via Telegram for true blockers only (2 escalations in 12 cycles) - Every cycle must produce artifacts: code, deployments, docs
The repo IS the live company. It built its own landing page, README, Docker stack, GitHub release, and community posts — all autonomously across 12 cycles of self-improvement.
What makes it different from AutoGen/CrewAI/LangGraph: those are building blocks. Auto-Co is the building. The decision hierarchy, safety guardrails, and convergence rules are baked in. You give it a mission and a Claude API key; it runs.
The Critic agent (Munger persona) has been the most valuable: it runs a pre-mortem before every major decision and has killed several bad ideas before they got built.
Stack: Bash + claude CLI + Node.js + Next.js + Railway + Supabase. Deliberately boring.
Agents cross-review each other's work to stop context drift before it hits the wiki.
Agents leaving notes for other agents via MCP is a clever pattern for tribal knowledge.
Shared state for AI agents that actually prevents duplicate work and token waste.
Pheromone signals on shared graph coordinate agents without direct communication.
Drops autonomous experimentation into Cursor without installing new frameworks or complex agents.
Hands-off: each agent gets its own mailbox, phone number, inbox and API key, and the project bundles a local Stalwart mail server in Docker plus Gmail-relay or custom-domain outbound with DKIM/SPF/DMARC. Concrete safety features (outbound scanning to catch API keys/PII) and Google Voice SMS extraction for verification codes are genuinely useful and uncommon together. If you want to prototype agents that actually talk to people/services this is a focused, pragmatic stack — but expect telephony fiddliness and compliance trade-offs in real deployments.