huddol
Run your own organization of agents
Runs with mockssource: GitHubPythonApache-2.0commit 0470d41a38f9
Python, Apache-2.0 licensed. The project labels itself: agent, agent runtime, agentic workflows, ai, ai agent, ai workspace, automation and fastapi.
huddol runs, with stand-ins for the services it depends on. An Argusic agent installed it in 12 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Huddol Rust CLI, Python core app (stdio and websocket), and webui all install and run. The core app accepts and responds to JSON-RPC requests over stdio, and listens on a loopback websocket port with token auth. The webui builds to production HTML/CSS/JS. Python test suite shows 954+ passed across 22 test files with 1 pre-existing sandbox-enforcement failure due to missing bubblewrap.
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 92 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.
- Node.js v18 too old for webui build (needs 20+)3 minutes
- No Rust toolchain installed2 minutes
- pnpm not available2 minutes
- Python 3.13 required but only 3.12 available2 minutes
- uv (Python package manager) not found1 minute
- bubblewrap (bwrap) sandbox binary not available and cannot be apt-installed (no root)1 minute
- Install time
- 12 minutes
- Cold machine to finish
- 30 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- echo '{"method":"ping","id":1}' | timeout 8 uv run python -m huddol --transport stdio returned {'type':'response','id':1,'result':{'pong':null}}; websocket mode launched and listened on 127.0.0.1:34033; cargo test -p huddol-cli passed 1/1; pnpm build completed with 2328 modules in 3s
- Model tokens used
- 98,284
- Exact commit tested
- 0470d41a38f9
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
exec /bin/sh -lc 'export PATH="$HOME/.local/bin:/home/runner/.cargo/bin:$PATH" && cd /work/repo/core && … succeeded in 22271ms: ........................................................................ [ 44%] ........................................................................ [ 66%] ........................................................................ [ 88%] .................................... [100%] 324 passed in 20.68s Now I have comprehensive data. Let me compile the final result. tokens used 98,284 Now I have comprehensive data. Let me compile the final result.
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
- Recovered from all 7 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 12 minutes to install, slower than the median of the 140 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 141 agent projects Argusic has installed and timed, huddol was the 96th fastest to reach a running state, and 94 of 141 reached one at all.
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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.19 |
Topics (from GitHub)
agentagent-runtimeagentic-workflowsaiai-agentai-workspaceautomationfastapillmmcpreactrusttauritauri-appworkflowworkflow-automation
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/huddol)Questions
- Does huddol run?
- huddol runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 12 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test huddol?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0470d41a38f9. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test huddol?
- The run that produced this verdict cost $0.19: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does huddol 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 huddol need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing huddol?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does huddol compare with the alternatives?
- Of the 141 agent projects Argusic has installed and timed, huddol was the 96th fastest to reach a running state, and 94 of 141 reached one at all.
- Where is the evidence for huddol?
- 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.