circleci-cli
Use CircleCI from the command line
Runssource: GitHubhomepageGoMITcommit a2e7dd1c5b90
Go, MIT licensed. The project labels itself: circle ci, circleci, cli, command line tool, continuous delivery, continuous integration, developer tools and devops.
circleci-cli runs. An Argusic agent installed it in 1 minute and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
circleci-cli builds from source with Go 1.27.1, the binary reports version and help, and all 7 clikit packages, all ~30 internal packages, and the full acceptance test suite (261s) pass.
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.
- go test -race compilation timeout (>5 min)6 minutes
- Go compiler not installed in container3 minutes
- Install time
- 1 minutes
- Cold machine to finish
- 27 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- go test -count=1 -timeout 600s ./acceptance/... exited 0 (entire suite passed); /tmp/circleci version returned 'circleci dev (a2e7dd1c5b90)'
- Model tokens used
- 462,124
- Exact commit tested
- a2e7dd1c5b90
- 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.
**Launch**: The binary executes and responds correctly: - `circleci version` → `circleci dev (a2e7dd1c5b90)` - `circleci help` → full help output with all command categories **Tests**: - `clikit/...` — 7 test packages, all passed - `internal/...` — 30+ test packages, all passed - `cmd/...` — 2 test packages, all passed - `acceptance/...` — full suite (261s), all passed (including version JSON/flag tests, help, comple… **Errors encountered**: - Go missing from container → fixed by downloading Go 1.27.1 tarball - Could not install system packages (no root) → worked around with prebuilt Go - Full test suite with `-race` was too slow (hit compilation timeout) → removed `-race` flag
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.
- Installed in 1 minute.
- Recovered from all 2 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
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 1 minutes after the clone.
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)
circle-cicircleciclicommand-line-toolcontinuous-deliverycontinuous-integrationdeveloper-toolsdevopsgolanggraphqltool
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/circleci-cli)Questions
- Does circleci-cli run?
- Yes. circleci-cli runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test circleci-cli?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a2e7dd1c5b90. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test circleci-cli?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does circleci-cli take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does circleci-cli need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing circleci-cli?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for circleci-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.