Behind-the-scenes of building FAOSX
View All Tags
Imagine ten senior engineers working on a complex project. Now imagine they can't talk to each other, don't know what the others are doing, and there's no project manager. That's what most multi-agent AI systems look like today—capable individuals creating chaos together.
The challenge isn't building smart agents. It's making them work as a team.
Ask ChatGPT to review your code, and you get generic feedback. Ask it to review your marketing copy, same tone. Ask it to plan your architecture, still the same voice. The AI is capable—but it's not specialized. It's like having one employee who claims to be an expert in everything.
In the real world, your best architect thinks differently than your best marketer. They use different vocabulary, apply different frameworks, and bring different perspectives. They've spent years developing intuition in their domains.
We asked ourselves: what if AI agents could work the same way?
When we started designing FAOSX, we had a whiteboard full of questions and zero answers.
Should agents be stateless or stateful? How do you coordinate ten agents without creating chaos? What happens when an agent makes a mistake at 2 AM? Where does the "intelligence" live—in the agent, the orchestrator, or somewhere in between?
AI assistants answer questions. Agentic systems get work done.
Last year, I watched a senior engineer spend three days coordinating a product launch. Not building. Not designing. Coordinating—pinging Slack channels, updating Jira tickets, chasing approvals, compiling status reports, scheduling meetings to discuss other meetings.
This is what enterprise work has become: talented humans doing robotic coordination work while AI chatbots answer trivia questions on the side.