runn
runn is a package/tool for running operations following a scenario.
Runs with mockssource: GitHubhomepageGoMITcommit 651af61c6e8d
Go, MIT licensed. The project labels itself: api testing, automation, buf, buf schema registry, chrome devtools protocol, db client, golang and grpc client.
runn runs, with stand-ins for the services it depends on. An Argusic agent installed it in 14 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
runn builds and runs: binary reports version 1.11.1, local + mock-github runbooks run with 0 failures, internal/fs GitHub/gist fetch tests pass against a locally stood-up schema-correct GitHub Enterprise mock, HTTP GitHub-API test passes end-to-end against that mock;
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 56 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.
- github:// and gist:// fetch tests fail with 'no credentials found' (real GitHub API/keys required)42 minutes
- TestHTTPRunnerRunUsingGitHubAPI fails with real GitHub 401 with placeholder token; its /users/{id} OpenAPI spec lacked a 401 response17 minutes
- go toolchain missing in container (go.mod requires go 1.26.8; no root for apt)5 minutes
- TestRunnerRenew and TestHostRules/CDP fail: exec google-chrome not found1 minute
- TestUseParentStore fails: no /var/run/docker.sock
- Install time
- 14 minutes
- Cold machine to finish
- 44 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- make build; ./runn -v (runn version 1.11.1); ./runn run 'github://k1LoW/runn/testdata/book/runn_0_success.yml' exit 0 (1 scenario, 0 skipped, 0 failures) against mock; ./runn run /tmp/demo/http.yml exit 0 (1 scenario, 0 skipped, 0 failures) vs live HTTP server; go test ./internal/fs/ ok (TestFetchPaths + TestFetchPathsAgainstMockGitHub PASS); go test -run TestHTTPRunnerRunUsingGitHubAPI PASS; go test -run TestHostRules/HTTP|gRPC|SSH PASS; go vet clean
- Model tokens used
- 3,508,882
- Exact commit tested
- 651af61c6e8d
- 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.
The full unit suite (`go test ./...`) still fails on exactly three environment-only gaps, all fixed… 1. `TestRunnerRenew` and the `CDP` subtest of `TestHostRules` exec `google-chrome`, which the conta… 2. `TestUseParentStore` requires a running Docker daemon (`/var/run/docker.sock`), which the contai… 3. `TestHostRules` fails only in its CDP subtest (which skips on `CI==1` on real CI); all other hos… Every fix I made was verified by re-running the targeted tests: internal/fs is green, the GitHub-AP… exec /bin/sh -lc 'date -u +%FT%TZ; echo "elapsed-minutes-check"' in /work/repo succeeded in 0ms: 2026-10-16T07:58:29Z elapsed-minutes-check tokens used 3,508,882
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 14 minutes.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
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.
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 | Runs with mocks | 92.00 | 0.31 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.15 |
Topics (from GitHub)
api-testingautomationbufbuf-schema-registrychrome-devtools-protocoldb-clientgolanggrpc-clienthacktoberfesthttp-clientload-testingscenario-testingssh-clienttest-helpertesting
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/runn)Questions
- Does runn run?
- runn runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 14 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test runn?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 651af61c6e8d. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test runn?
- The run that produced this verdict cost $0.31: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does runn take to install?
- 14 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 runn need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing runn?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for runn?
- All 2 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.