jido
🤖 Autonomous agent framework for Elixir. Built for distributed, autonomous behavior and dynamic workflows.
Runssource: GitHubhomepageElixirApache-2.0commit 6244d7691cbe
Elixir, Apache-2.0 licensed. The project labels itself: agent framework, ai agents, core, elixir, elixir package, event driven architecture, jido and orchestration.
jido runs. An Argusic agent installed it in 12 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Elixir 1.18.5 + Erlang/OTP 25 installed under ~/local_erlang and ~/elixir; mix deps.get, mix compile, and mix test all succeed with 2470 passing tests and 0 failures.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- No Erlang/OTP or Elixir runtime installed in container; apt packages too old and no sudo2 minutes
- mix deps.compile poolboy failed because rebar3 calls erl with hardcoded /usr/lib/erlang path1 minute
- Install time
- 12 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- mix test completed: 2470 tests, 0 failures, 187 excluded in 109s (first run) and 113s (second verification run)
- Model tokens used
- 65,778
- Exact commit tested
- 6244d7691cbe
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
date +%s' in /work/repo succeeded in 116850ms: Erlang (SMP,ASYNC_THREADS) (BEAM) emulator version 13.2.2.5 Erlang/OTP 25 [erts-13.2.2.5] [source] [64-bit] [smp:256:4] [ds:256:4:10] [async-threads:1] [jit:ns] Elixir 1.18.5 (compiled with Erlang/OTP 25) Finished in 113.3 seconds (62.2s async, 51.1s sync) 2470 tests, 0 failures, 187 excluded 1791207119 Confirmed again - all 2470 tests pass. Total elapsed time was about 12 minutes from start to finish… tokens used 65,778 Confirmed again - all 2470 tests pass. Total elapsed time was about 12 minutes from start to finish…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Took 12 minutes to install, slower than the median of the 17 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 18 agent-framework projects Argusic has installed and timed, jido was the 13th fastest to reach a running state, and 11 of 18 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
agent-frameworkai-agentscoreelixirelixir-packageevent-driven-architecturejidoorchestrationworkflow
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/jido)Questions
- Does jido run?
- Yes. jido runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test jido?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6244d7691cbe. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test jido?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does jido take to install?
- 12 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does jido need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing jido?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does jido compare with the alternatives?
- Of the 18 agent-framework projects Argusic has installed and timed, jido was the 13th fastest to reach a running state, and 11 of 18 reached one at all.
- Where is the evidence for jido?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.