Live data from Hacker News

Show HN: Jido 2.0, Elixir Agent Framework

jido.run

1–10 of 74 posts

Show HN: Jido 2.0, Elixir Agent Framework

#1
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!

Show HN: Jido 2.0, Elixir Agent Framework
jido.run

Re: Show HN: Jido 2.0, Elixir Agent Framework

#2
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-...

Re: Show HN: Jido 2.0, Elixir Agent Framework

#3
post #2

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-...

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.

Re: Show HN: Jido 2.0, Elixir Agent Framework

#5
post #2

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-...

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.

( 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.

Re: Show HN: Jido 2.0, Elixir Agent Framework

#6
post #5

Earlier quoted context omitted.

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.

( 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.

I'll put something together!

Re: Show HN: Jido 2.0, Elixir Agent Framework

#7
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: "my_agent",
    description: "A simple agent",
Post reply on HN