agentjido/jido
This system is a comprehensive agent orchestration framework that manages the lifecycle, state, and communication of autonomous software agents. It provides a structured runtime for defining agents with customizable plugins, memory, and scheduling capabilities, while supporting dynamic topology management and durable state persistence. The framework emphasizes observability, testing, and developer ergonomics through code generation and comprehensive documentation.
64.8
Adequate · 4 August 2026
25k
lines of production code
Elixir
primary language
1
bus factor · 25 authors in all
5
measurements over time
How it got here
2024 · Jido 2.0 architecture and test overhaul
The project underwent a major architectural shift to Jido 2.0, replacing the global singleton model with an instance-scoped design that supports multiple independent Jido instances. This period focused on implementing the new runtime, action system, and plugin infrastructure while removing legacy workflow modules. Comprehensive test suites were added to validate the new core components, alongside updated documentation and dependency configurations.
17 changes
2025–2026 · core infrastructure and observability
This period focused on establishing the foundational runtime components of the Jido framework, introducing structured agent lifecycle management, plugin configuration, and in-memory state handling. Significant effort was dedicated to implementing durable storage adapters, a cron scheduler, and a hot-swappable pod topology system. The work was heavily supported by comprehensive test coverage and the introduction of a centralized observability and tracing infrastructure.
29 changes
Survey your own repository
agentjido/jido was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 4 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit b0914cf0fc — the exact code this score is about.
- Scored under rubric rubric-2026.08.19. Score the same commit under that rubric and you get the same number.