huginn
Create agents that monitor and act on your behalf. Your agents are standing by!
Runssource: GitHubRubyMITcommit 5658f26d4c17
Ruby, MIT licensed. The project labels itself: agent, automation, feed, feedgenerator, huginn, monitoring, notifications and rss.
huginn runs. An Argusic agent installed it in 27 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Huginn Rails app boots with PostgreSQL on port 3000, all 2047 non-feature specs pass, API returns HTTP 200
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.
- mysql2 native extension failed - no MySQL client headers5 minutes
- fontawesome CSS asset missing on home page1 minute
- URL polyfill not found for JavaScriptAgent1 minute
- Install time
- 27 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- bundle exec rspec spec/ --exclude-pattern=features exited 0, 2047 examples 0 failures; curl localhost:3000 returned 200
- Model tokens used
- 80,831
- Exact commit tested
- 5658f26d4c17
- 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.
Randomized with seed 38120
All 2047 specs pass with 0 failures. Also verified the app server returns HTTP 200. Let me stop the…
exec
/bin/sh -lc 'pkill -f puma 2>/dev/null; true' in /work/repo
exited 143 in 0ms:
All 2047 non-feature specs pass with 0 failures, and the app server responds with HTTP 200.
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 2…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 27, "errors": [{"msg": "my…
tokens used
80,831Replay 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 3 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 MIT, as reported by its host.
What did not, or is not known
- Took 27 minutes to install, slower than the median of the 74 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 75 agent projects Argusic has installed and timed, huginn was the 65th fastest to reach a running state, and 51 of 75 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)
agentautomationfeedfeedgeneratorhuginnmonitoringnotificationsrssscrapertwittertwitter-streamingwebscraping
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/huginn)Questions
- Does huginn run?
- Yes. huginn runs. Argusic installed and launched it on a clean machine in 27 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test huginn?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5658f26d4c17. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test huginn?
- The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does huginn take to install?
- 27 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 huginn need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing huginn?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does huginn compare with the alternatives?
- Of the 75 agent projects Argusic has installed and timed, huginn was the 65th fastest to reach a running state, and 51 of 75 reached one at all.
- Where is the evidence for huginn?
- 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.