The Missing Primitive for Agent Swarms#
AI Engineer Europe 2026 digest Program Adjacent pick 8–10 April 2026
Lou Bichard — Ona
- Why: Multi-agent coordination is currently reinvented per framework with brittle scaffolding (threads, worktrees, container pools); the argument that swarms need a platform primitive — identity, isolation, lifecycle, resource limits — is a cloud-native systems question, not an application one.
- What: A case for treating swarms as an infrastructure category: why current approaches break at scale, what a proper swarm primitive looks like (spawnable isolated agent execution contexts with identity, resource limits, and coordination semantics), lessons from shipping this to enterprises at Ona, and the UX of interacting with fleets of agents.
- How: Platform-level spawn semantics for isolated execution contexts, rather than application-level thread and state management.
- Where applicable: Teams building multi-agent systems in production. Conceptual plus one company's enterprise experience; no published validation stated in the abstract.