cli
A command-line interface for Hetzner Cloud
Runs with mockssource: GitHubGoMITcommit 883500841121
Go, MIT licensed. The project labels itself: cli, command line, command line tool, commandline interface, hcloud, hetzner and hetzner cloud.
cli runs, with stand-ins for the services it depends on. An Argusic agent installed it in 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.
hcloud CLI binary builds and runs, printing version 1.69.0-dev and full help output. The complete internal test suite (34 packages) passes with zero 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 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.
- Go toolchain not installed in container (missing: go binary)3 minutes
- Install time
- 5 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- go test on all 34 internal test packages: all returned 'ok' with zero failures; binary runs: 'hcloud version' prints 'hcloud 1.69.0-dev'; 'hcloud --help' prints full usage text
- Model tokens used
- 55,506
- Exact commit tested
- 883500841121
- 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.
"github.com/spf13/cobra"
"github.com/hetznercloud/cli/internal/cli"
"github.com/hetznercloud/cli/internal/state"
"github.com/hetznercloud/cli/internal/state/config"
"github.com/hetznercloud/hcloud-go/v2/hcloud"
"github.com/hetznercloud/hcloud-go/v2/hcloud/exp/kit/randutil"
)
var client = hcloud.NewClient(hcloud.WithToken(os.Getenv("HCLOUD_TOKEN")))
All 34 test packages pass (0 failures). The binary builds and runs (`hcloud version` prints `hcloud…
tokens used
55,506
All 34 test packages pass (0 failures). The binary builds and runs (`hcloud version` prints `hcloud…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 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, 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 5 minutes to install, slower than the median of the 60 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 61 cli projects Argusic has installed and timed, cli was the 37th fastest to reach a running state, and 55 of 61 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.07 |
Topics (from GitHub)
clicommand-linecommand-line-toolcommandline-interfacehcloudhetznerhetzner-cloud
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cli)Questions
- Does cli run?
- cli runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 5 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test cli?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 883500841121. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test cli?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does cli take to install?
- 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 cli need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing cli?
- 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 cli compare with the alternatives?
- Of the 61 cli projects Argusic has installed and timed, cli was the 37th fastest to reach a running state, and 55 of 61 reached one at all.
- Where is the evidence for cli?
- 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.