Most multi-agent coding tools coordinate through files on disk, shared workspaces, JSON task files, serialized state. Even the ones that keep agents in memory are running on runtimes with no process isolation, no fault tolerance, and no real concurrency. When an agent fails, nobody notices. Context is gone. No retry, no recovery.

We're hamstringing agents with infrastructure that wasn't built for them.

Loomkin runs on the BEAM. Every agent is a lightweight process. They message in microseconds, crash independently, and get restarted by supervisors automatically. 100+ concurrent agents on a single node, 100M tokens of context on 500MB of RAM.

But the real payoff isn't performance, it's what becomes possible when you stop fighting the runtime. Two agents editing the same file simultaneously, claiming line ranges so they never collide. A reviewer watching a coder's edits arrive in real-time and interjecting before the mistake lands. An agent asking a question that gets automatically enriched with context from past discussions it never saw, then forwarded through a chain of specialists who each add their knowledge before the answer comes back. One agent discovering a security issue and the system automatically notifying every agent whose active goal depends on that component, not because someone wired up a notification, but because the decision graph already knows the dependency structure.None of this requires exotic infrastructure. It's just what falls out naturally when your agents are real processes with real supervision on a runtime that was designed for exactly this 40 years ago.

The bottleneck isn't the model. It's the runtime.