Why I Built OpenRig

01 — The Anxiety Here's how it actually happens. You start with one agent. Then you open another tab, a second agent working on a different task. The first one sets up tmux connections so they can talk. You add a third. A fourth. Over the course of a few days, you've built an organic topology: an orchestrator that's been refining its understanding of your architecture over three continuous days, a review agent that's reviewed 40+ PRs and developed a deep sense of your codebase patterns, and research agents that have built up a knowledge base on technology evaluations you need. You're not tracking all of this consciously. The agents are managing their own connectivity. You're bouncing around, orchestrating, occasionally checking in. Then you need to reboot your machine. Memory's swapping. Performance is bad. Security update you've been putting off. But your agents are cooking. And you're genuinely worried that if you stop now, you won't be able to get back to where you are. The sessions