AutoKuma
AutoKuma is a utility that automates the creation of Uptime Kuma monitors based on Docker container labels. With AutoKuma, you can eliminate the need for manual monitor creation in the Uptime Kuma UI.
Could not verifysource: GitHubRustMITcommit 1cba1f0e12ce
Rust, MIT licensed. The project labels itself: docker, monitor, monitoring, selfhosted, socket io, uptime, uptime kuma and uptime monitoring.
Argusic could not get AutoKuma running. An Argusic agent installed it in 3.5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Full Rust workspace builds and all 84 unit tests pass; kuma CLI binary displays help and version; autokuma binary starts and connects logic (fails gracefully without a real Uptime Kuma server).
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 80 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.
- kuma-client/src/client.rs doctest had async code in a non-async context, referencing types not imported in the doctest scope (Client, Config, Url, TagDefinition, MonitorGroup, Tag, Notification, MonitorHttp)2 minutes
- Install time
- 4 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- Model tokens used
- 99,753
- Exact commit tested
- 1cba1f0e12ce
- 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.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
running 2 tests test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s running 0 tests test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s running 8 tests test result: ok. 8 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s running 1 test test result: ok. 0 passed; 0 failed; 1 ignored; 0 measured; 0 filtered out; finished in 0.00s All good. Let me compute the elapsed time and produce the final report. tokens used 99,753 All good. Let me compute the elapsed time and produce the final report.
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
- Installed in 3.5 minutes.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 4 times, so the result is not a one-off.
What did not, or is not known
- An agent with no time limit did not get it running.
Of the 9 docker projects Argusic has installed and timed, AutoKuma was the 5th fastest to reach a running state, and 8 of 9 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 | 2/3 | Ran out of time | 0.00 | 0.13 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.03 | |
| Argusic Runner | 2/3 | Ran out of time | 0.00 | 0.38 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.10 |
Topics (from GitHub)
dockermonitormonitoringselfhostedsocket-iouptimeuptime-kumauptime-monitoringwebsocket
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/autokuma)Questions
- Does AutoKuma run?
- Argusic could not verify that AutoKuma runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test AutoKuma?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1cba1f0e12ce. 4 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test AutoKuma?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does AutoKuma take to install?
- 3.5 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 AutoKuma need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing AutoKuma?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does AutoKuma compare with the alternatives?
- Of the 9 docker projects Argusic has installed and timed, AutoKuma was the 5th fastest to reach a running state, and 8 of 9 reached one at all.
- Where is the evidence for AutoKuma?
- All 4 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.