cli-printing-press
Every API has a secret identity. This finds it, absorbs every feature from every competing tool, then builds the GOAT CLI, designed for AI agents first, with SQLite sync, offline search, and compound insight commands.
Could not verifysource: GitHubGoMITcommit 782bb11f2457Under review
Go, MIT licensed. The project labels itself: ai agents, cli, cli generator, developer tools, golang and openapi.
Argusic could not get cli-printing-press running. An Argusic agent hit no errors on a clean machine with no GPU, and the whole session was recorded.
Measured by Argusic on a fresh machine every time. Every number links to its evidence.
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.
- Exact commit tested
- 782bb11f2457
- Container image
- sha256:4c3d41857be3
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.
- Install time
- the run did not report one
- Cold machine to finish
- the attempt was stopped at the time limit after 42 minutes, so it never finished
- Errors hit and fixed
- the attempt was cut off at the time limit before it reported what it had hit
- 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
- Model tokens used
- not recorded for this run
- 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
- the attempt did not get far enough to verify anything before the time limit
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 15534ms: go version go1.27.1 linux/amd64 Go is installed. Now let me set up PATH and env vars for the session, then build the project. exec /bin/sh -lc "cat >> /home/runner/.bashrc <<'EOF' export PATH=\"/home/runner/go-sdk/bin:/home/runner/go/bin:"'$PATH" export GOPATH="/home/runner/go" EOF export PATH="/home/runner/go-sdk/bin:/home/runner/go/bin:$PATH" export GOPATH="/home/runner/go" cd /work/repo && go build -o ./cli-printing-press ./cmd/cli-printing-press 2>&1 | tail -100' in /wo… Build is running in background (first build downloads modules). Let me wait for it.
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
- Nothing broke on the way: zero errors between clone and running.
- Licensed MIT, as reported by its host.
- Measured 3 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.
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 Runnerescalation | 1/3 | Ran out of time | 0.00 | 0.87 | |
| Argusic Runner | 2/3 | Ran out of time | 0.00 | 0.05 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.05 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cli-printing-press)Questions
- Does cli-printing-press run?
- Argusic could not verify that cli-printing-press runs. Argusic installed and launched it on a clean machine, hitting 0 errors on the way, and recorded the session.
- How did Argusic test cli-printing-press?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 782bb11f2457. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test cli-printing-press?
- The run that produced this verdict cost $0.87: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- Does cli-printing-press need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing cli-printing-press?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for cli-printing-press?
- All 3 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.