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 62 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Huginn Rails app runs on localhost:3000 returning HTTP 200, admin login with seeded credentials works, the Agents page returns 200, and the full rspec suite passes 2047/2047 examples.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$1.03 (measured)
recorded runs
2
last tested
stars
50,598
forks
4,361
open issues
690
watchers
727
size
12 MB
created
last push

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.

Time lost to each failure while testing huginn, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • No Ruby runtime available in container30 minutes
  • mysql2 gem failed to build (no MySQL client dev headers)8 minutes
  • No MySQL server available8 minutes
  • Font Awesome CSS missing (npm deps not installed)6 minutes
  • 5 rspec failures: URL polyfill tmp/build/url-polyfill.js missing2 minutes
Install time
62 minutes
Cold machine to finish
68 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
bundle exec rspec exited 0 with 2047 examples, 0 failures; curl http://localhost:3000/ returned 200; curl http://localhost:3000/agents with a logged-in session returned 200
Model tokens used
359,628
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.

- Built Ruby 3.4.8 from source (no system Ruby available; compiled libyaml for psych, zlib headers …
- Extracted MySQL 8.0.46 server + client from Ubuntu `.deb` packages (no root access), initialized …
- `bundle install` completed: 274 gems
- `rake db:create`, `db:migrate`, `db:seed` completed (admin user + 7 example agents)
- `npm install` + `npm run build` completed (fontawesome + URL polyfill)
**Errors found and fixed:**
- No Ruby runtime → built 3.4.8 from source with workarounds for missing dev headers
- `bundle` failed on missing zlib → compiled `zlib.so` and installed to extension path
- `mysql2` gem failed → downloaded `libmysqlclient-dev` and `libmysqlclient21` debs, pointed bundle…
- No MySQL server → extracted `mysqld` + deps from Ubuntu packages, initialized datadir, started on…
- Server 500s: fontawesome CSS missing → `npm install`; `application.css` not in precompile list → …
- 5 rspec failures on missing `tmp/build/url-polyfill.js` → `npm run build`

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 5 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.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 62 minutes to install, slower than the median of the 138 comparable projects Argusic has measured.

Of the 139 agent projects Argusic has installed and timed, huginn was the 138th fastest to reach a running state, and 93 of 139 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.001.03
Argusic Runner1/3Runs100.000.14

Topics (from GitHub)

agentautomationfeedfeedgeneratorhuginnmonitoringnotificationsrssscraperwebscraping

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/huginn.svg)](https://argusic.com/subject/huginn)

Questions

Does huginn run?
Yes. huginn runs. Argusic installed and launched it on a clean machine in 62 minutes, hitting 5 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. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test huginn?
The run that produced this verdict cost $1.03: 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?
62 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?
5 things broke in the recorded run, and 5 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 139 agent projects Argusic has installed and timed, huginn was the 138th fastest to reach a running state, and 93 of 139 reached one at all.
Where is the evidence for huginn?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion