jido
Jido, from the Japanese for automatic, is an autonomous agent framework for Elixir. It treats agent systems as ordinary Elixir and OTP software: agents hold state and implement cmd/2, actions do work and transform that state, signals route events, and directives describe effects for the runtime to execute. AI is optional; the core gives you the agent architecture and runtime.
The README frames it as a formalized pattern on top of GenServer rather than a replacement. Agents are immutable data structures in an Elm/Redux style, with schema-validated state. cmd/2 takes an action and returns the updated agent plus directives, and built-in directives include Emit, Spawn, SpawnAgent, StopChild, Schedule and Stop. An AgentServer runs agents in production with parent-child hierarchies, signal routing strategies and instance-scoped supervision for multi-tenant deployments.
It is the core of a wider ecosystem: req_llm as an LLM HTTP client, jido_action for validated actions with tool integration, jido_signal for CloudEvents-based messaging, and jido_ai for model integration. Add {:jido, "~> 2.0"} to mix.exs. Apache-2.0 licensed, with demos at jido.run.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-10-17
- Commits, last 90 days
- 27
- Releases, last 90 days
- 4
- Latest release
- v3.0.0-beta.2 (2026-10-19)
- Open issues
- 4
- Recent issues with at least one comment
- 16/24
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #379 V3: verify Bedrock persistence, recovery, and S3 fixes0 comments · 2026-09-15
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Compatibility
Use cases
Alternatives
Comments
No comments yet. Be the first!