Live data from Hacker News

Show HN: Jido 2.0, Elixir Agent Framework

jido.run

71–74 of 74 posts

Re: Show HN: Jido 2.0, Elixir Agent Framework

#71
post #61

Legit question, am I missing anything not playing with agents? Like, what's the killer-app feature vs chatgpt prompt?

Its an order of magnitude difference in what it can do, mostly because it can verify its own work. It can also use subagents which helps a lot. Large tasks I usually have done by subs with the main agent directing. This means the task they can take on can be much larger.

I'm in the same boat as waynesonfire and I'm afraid this doesn't answer the question sufficiently. What do you do with an agent? What's a concrete example vs. typing in a chat box.

Re: Show HN: Jido 2.0, Elixir Agent Framework

#72
Nice work shipping this. The BEAM's fault tolerance model makes a lot of sense for agent workloads, been thinking about similar tradeoffs on the orchestration side. Curious what the failure recovery looks like when an agent mid-run hits a bad LLM response vs. a process crash.

Re: Show HN: Jido 2.0, Elixir Agent Framework

#73
post #71
post #61

Earlier quoted context omitted.

Its an order of magnitude difference in what it can do, mostly because it can verify its own work. It can also use subagents which helps a lot. Large tasks I usually have done by subs with the main agent directing. This means the task they can take on can be much larger.

I'm in the same boat as waynesonfire and I'm afraid this doesn't answer the question sufficiently. What do you do with an agent? What's a concrete example vs. typing in a chat box.

When you have workflows that you repeat over and over it’s easier to formalize with something like jido. Ie if you don’t want to type into a checkbox and verify output everytime.
Post reply on HN