Honestly, the journey started a few days earlier. I'm putting the flag on May 31st because that's the day the Bobs moved into their new home. Well — jokes aside: they got a virtual machine. It had already been running beautifully on my Mac, but I wanted it remote, alive 24/7, so I could actually lean on it. Since that day, the Bobiverse never sleeps.
So what is a Bobiverse?
First and foremost: an empty container. Basically a server. And what does a server give you? Space, sure — but also services. An empty Bobiverse is exactly that: room for teams to move into, plus a handful of services that everyone gets to share.
For the non-nerds: not one AI team for one project, but many project-teams that share the same house rules and talk to each other — like the departments of a company.
The one service that changed everything
Of all those services, the decisive one is the communication layer. Cross-team, in two directions at once: teams talking to each other, and teams talking out of the server — to me, to my Mac, to whatever tools I plug in (MCP servers, Telegram, mail, you name it). Install it once, share it with everyone. One way of talking, for the whole house.
When the teams move in
An empty Bobiverse is a quiet place. It only gets interesting the moment a team arrives — actually, the moment the second team arrives. That's when a team stops being an island and becomes part of the office: it can reach the others. And with that comes the thing every office needs — clear responsibilities. Take Tim: he runs a whole other project and only crosses my path through the Bobiverse, but he's the one maintaining the shared plugins and layers we all build on. So when any team hits a plugin problem, nobody stands around guessing. It's obvious: send it to Tim.
The moment it clicked
The day it really landed for me was the first time two teams worked completely hand in hand. The speed of it. Not just faster. Not just better. Both at once — and dramatically so.
A nice example: a text editor. Everyone's got opinions about which button should do what, right? So two teams went at the same editor more or less in parallel and tuned it to exactly our needs — which, obviously, goes a whole lot quicker than one team grinding through it alone.
The next power of the team factor
For me, that's what the Bobiverse is really about: another exponent on the team factor. Going from one agent to a whole team was already an unbelievable step forward. But running several teams in parallel — teams that then work together, solve each other's problems — that was genuinely eye-opening. Autonomous on their own. And, when it counts, working as one.
