Jido 2.0, Elixir Agent Framework

Mike Hostetler looked at the AI agent landscape and saw a problem nobody else was talking about: every major agent framework was built on runtimes that fundamentally weren't designed for this. TypeScript frameworks? "Single-threaded event loops trying to juggle concurrent agents with promises and prayer." Python? Better, but "after a long time they couldn't stay up." Meanwhile, the BEAM—the Erlang virtual machine that's powered telecom infrastructure for decades—was sitting there, built explicitly for massive concurrent workloads with built-in fault tolerance. It was the elephant in the room nobody wanted to acknowledge. So Mike built Jido.

Jido 2.0 just shipped after 18 months of iteration, and it's a complete rethink of what an agent framework should look like on the BEAM. The original 1.0 was overengineered—Mike admits he was still learning OTP in depth and it showed. Too many abstractions, too much friction, people wanted to build agents not fight the framework. So he stripped it down to something elegant: agents are just data, a struct with state actions and tools that runs inside a GenServer. Everything flows through a single function, cmd/2. Actions go in, an updated agent and directives come out. Side effects are typed data structures, not hidden magic. This isn't a toy—it's production-hardened with full supervision trees, multi-agent support across distributed processes, and serious observability with OpenTelemetry baked in.

The reasoning strategies alone should make people pay attention: ReAct, Chain of Thought, Tree of Thought—all running on a runtime that actually handles concurrency properly. Plus agentic memory, MCP integration, sensors for external services, and a persistence layer that keeps agents durable. It's got tool calling, agent skills, advanced workflows. The whole agentic feature set. Mike's thesis is simple: the BEAM was built for exactly this kind of work, and after 18 months of living in that world, that bet is paying off. The community is growing, people are building. If you've been waiting for an agent framework that treats concurrency like it matters instead of hacking it on top of a general-purpose runtime, this is your sign.