linode-cli

The official Linode command line interface.

Runs with mockssource: GitHubhomepagePythonBSD-3-Clausecommit 251dbbc6a325

Python, BSD-3-Clause licensed. The project labels itself: cloud, command line tool, infrastructure and linode.

linode-cli runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.3 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The linode-cli installs, builds from its OpenAPI spec, and passes all 233 unit tests; the CLI binary prints help, version, and command listings on demand without requiring real API credentials.

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

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
1
last tested
stars
442
forks
163
open issues
27
watchers
26
size
3 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 linode-cli, 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.

  • Baked spec file data-3 missing from repository and initial pip install — CLI could not load any commands0.2 minutes
Install time
under a minute
Cold machine to finish
2 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
make test-unit: 233 passed in 1.23s; linode-cli --help returned full usage; linode-cli --version returned 'linode-cli 0.0.0.dev Built from spec version 4.229.1'; linode-cli linodes --help listed all actions; from linodecli import main succeeded outside source tree with LINODE_CLI_TEST_MODE=1
Model tokens used
40,049
Exact commit tested
251dbbc6a325
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.

- Unit tests pass 233/233
tokens used
40,049
Here's the summary of everything I did and observed.
**Process:**
- Read the README, CONTRIBUTING, Makefile, and AGENTS.md
- Set up a Python virtualenv, installed `.[dev,obj]` dependencies
- The baked spec file (`data-3`) was missing from the repo and the initial installed package, causi…
- Ran `make bake SPEC_VERSION=latest` — this downloaded the OpenAPI spec from GitHub (no token need…
- Ran `make install` — this rebuilt the distribution wheel with the baked data and reinstalled it
- Verified the CLI launches with full command help and version output
- Unit tests pass 233/233

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 0.3 minutes.
  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed BSD-3-Clause, 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.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 Runner1/3Runs with mocks92.000.02

Topics (from GitHub)

cloudcommand-line-toolinfrastructurelinode

Embed the badge

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

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

Questions

Does linode-cli run?
linode-cli runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 0 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test linode-cli?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 251dbbc6a325. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test linode-cli?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does linode-cli take to install?
0.3 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 linode-cli need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing linode-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.
Where is the evidence for linode-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.

Discussion