Show HN: Jido 2.0, Elixir Agent Framework

96•mikehostetler•1h ago

Hi HN!

I'm the author of an Elixir Agent Framework called Jido. We reached our 2.0 release this week, shipping a production-hardened framework to build, manage and run Agents on the BEAM.

Jido now supports a host of Agentic features, including:

- Tool Calling and Agent Skills - Comprehensive multi-agent support across distributed BEAM processes with Supervision - Multiple reasoning strategies including ReAct, Chain of Thought, Tree of Thought, and more - Advanced workflow capabilities - Durability through a robust Storage and Persistence layer - Agentic Memory - MCP and Sensors to interface with external services - Deep observability and debugging capabilities, including full stack OTel

I know Agent Frameworks can be considered a bit stale, but there hasn't been a major release of a framework on the BEAM. With a growing realization that the architecture of the BEAM is a good match for Agentic workloads, the time was right to make the announcement.

My background is enterprise engineering, distributed systems and Open Source. We've got a strong and growing community of builders committed to the Jido ecosystem. We're looking forward to what gets built on top of Jido!

Come build agents with us!

Comments

davidw•1h ago

It'd be cool to see a screenshot of what 'observer' shows as the process tree with a few agents active.

Edit: for those not familiar with the BEAM ecosystem, observer shows all the running Erlang 'processes' (internal to the VM). Here are some examples screenshots on one of the first Google hits I found:

https://fly.io/docs/elixir/advanced-guides/connect-observer-...

mikehostetler•1h ago

We have a full dashboard called `jido_studio` that will be available soon that helps visualize it.

Teaser screenshot is here: https://x.com/mikehostetler/status/2025970863237972319

Agents, when wrapped with an AgentRuntime, are typically a single GenServer process. There are some exceptions if you need a larger topology.

davidw•1h ago

( https://xcancel.com/mikehostetler/status/2025970863237972319 for people who don't like supporting the white supremacist site )

I was curious about the actual BEAM processes though, that you see via the observer application in Erlang/Elixir.

mikehostetler•1h ago

I'll put something together!

StevenNunez•1h ago

A library I'm excited to not vibecode against!

mmcclure•59m ago

I haven't used Jido for anything yet, but it's one of those projects I check in on once a month or so. BEAM does seem like a perfect fit for an agent framework, but the ecosystem seeming limited has held me back from going too far down that path. Excited to see 2.0!

Just a heads up, some of your code samples seem to be having an issue with entity escaping.

    name: &quot;my_agent&quot;,
    description: &quot;A simple agent&quot;,

whalesalad•44m ago

oh no did HN traffic defeat OTP

enraged_camel•44m ago

Where does this stand in relation to LangChain? https://github.com/brainlid/langchain

(Probably complimentary but wanted to check)

mmcclure•29m ago

I went down this path a bit the other night, curious what OP's answer is. My mental model was that they could be complimentary? Jido for agent lifecycle, supervision, state management, etc, LangChain for the LLM interactions, prompt chains, RAG, etc. Looks like you could do everything in Jido 2.0, but if you like/are familiar with LangChain it seems like they could work well together.

klocksib•44m ago

The site seems to be getting hugged to death, here's the archive.org backup:

https://web.archive.org/web/20260305161030/https://jido.run/

memco•17m ago

Not sure if related, but the page loads fine and then after a few seconds refreshes into a 404. I gave up trying to read the article.

mmcclure•7m ago

I was seeing the same thing. Looking at the network tab, I suspect there's LiveView involved and that dying from load isn't getting handled well.

carverauto•40m ago

Going to give it a shot this weekend

rvz•35m ago

Let me guess, in the next 6 months, Elixir and Erlang becoming fashionable to build AI agents and then another hype cycle of AI usage and marketing of Elixir.

What's old is now rebranded, reheated and new again.

bhekanik•35m ago

Nice work shipping this.

I’ve found the hardest part with agent frameworks isn’t model plumbing, it’s operational boundaries: how you isolate tools, enforce time/budget limits, and recover from partial failures when an agent call chain fans out.

BEAM’s supervision model feels like a genuinely strong fit for that, especially if each tool execution can be treated as a supervised unit with clear restart/escalation semantics. Curious whether you’ve seen teams default to many small specialized agents vs fewer general agents with stricter policies.

malkosta•33m ago

How do you ensure security? Does it have a proper container? Otherwise, it's impossible to prevent leaking prod secrets.

maxekman•11m ago

Thanks for sharing! I’ll definitely check it out.

I just LLM-built an A2A package which is a GenServer-like abstraction. I however missed that there already was another A2A implementation for Elixir. Anyway, I decided to leave it up because the package semantics were different enough. Here it is if anyone is interested: https://github.com/actioncard/a2a-elixir