Is there any support for parallelism in Jido?
Nothing explicit other than Jido.Exec having both a run/4 and run_async/4 methods.
The vision is to utilize existing OTP patterns for any concurrency. I’m working on publishing a Roadmap - but here’s the gist:
- DONE - Stateless Agents
- This is the foundation of Agents as data structures only with
Jido.Execfocused on safely executing a single Action at a time
- This is the foundation of Agents as data structures only with
- 98% DONE - Stateful Agents
- This milestone wraps a GenServer around the Stateless Agent and adds the
Jido.Signalas the foundation for inter-process communication - No parallelization at this layer other then
cast/2to call an Agent with a Signal, receive arefand wait for the Agent to send you the result of the Action - but this is more async then parallel
- This milestone wraps a GenServer around the Stateless Agent and adds the
- 50% - Orchestrated Agents
- This is what I’ve been working on the last few weeks and is the mode where a lead agent orchestrates child agents towards accomplishing its objective
- The centerpiece of this layer is a runtime-based workflow orchestrator that coordinates and optimizes multi-agent signals in parallel - no explicit parallel coordination will be required - you get it for free
- You can see some of the brainstorming here: Mike Hostetler // Chief Agent Officer on X: "You have 1 second to look at this code Is it obvious? If not, what is confusing? https://t.co/fFYS5lvM2O" / X
After orchestrated agents are done, there will be plenty of work building out extras and examples.
In Jido’s current state, I would create an Action that wraps Jido.Exec.run_async calls to the 3 actions you want to run in parallel - then await the results of all three before returning itself.
Here’s a quick gist that Claude built for me to model this: Parallel Jido Actions · GitHub
Let me know if that works for you and I’ll whip up a guide for this and throw together a Livebook to put into the Workbench cookbook permanently.
Good luck!
