radian runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 28 minutes, hitting 5 errors on the way, and recorded the session.

How did Argusic test radian?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 545f504f672d. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test radian?

The run that produced this verdict cost $0.23: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does radian take to install?

28 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 radian need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing radian?

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 radian?

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.

radian

A 21 century R console

Runs with mockssource: GitHubPythonMITcommit 545f504f672d

Python, MIT licensed. The project labels itself: cli, console, ipython, radian, repl and terminal.

radian runs, with stand-ins for the services it depends on. An Argusic agent installed it in 28 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

radian 0.7.1 installed via pip, uses R 4.3.3 extracted from Ubuntu debs. 15 of 22 automated tests pass. R console launches interactively (test_aaa confirms prompt). CRAN-based features (reticulate Python mode, askpass, renv) untested due to no CRAN mirror access.
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.23 (measured)
recorded runs: 2
last tested: 2026-10-04
stars: 2,291
forks: 89
open issues: 32
watchers: 23
size: 2 MB
created: 2017-03-31
last push: 2026-10-03

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-04. 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 radian, 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.

CRAN packages (askpass, renv, reticulate) required by 7 tests cannot be installed10 minutes
No R binary or shared library available in container5 minutes
rchitect exec_host re-exec loses LD_LIBRARY_PATH entries for extracted R installation5 minutes
R default packages (utils, stats) fail to load with invalid editor error3 minutes
R binary fails to load due to missing libtirpc.so.32 minutes

Install time: 28 minutes
Cold machine to finish: 30 minutes
Errors hit and fixed: 5 hit, 5 fixed with no human help
How the result was proved: python3 -m radian --version returns radian version 0.7.1, r version 4.3.3. pytest runs 22 tests, 15 pass, 7 fail
Model tokens used: 221,129
Exact commit tested: 545f504f672d
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.

echo \"  test_renv - needs R package 'renv' (not available)\"
echo \"  test_reticulate, test_multiline, test_ctrl_d, test_completion - need R package 'reticulate…
echo \"  test_startup - cursor expected (4,3) got (4,5) due to extra R warning lines\"" in /work/re…
 exited 137 in 0ms:
```json
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 28, "errors": [{"msg": "No…
```
tokens used
221,129
```json
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 28, "errors": [{"msg": "No…
```

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 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.
Took 28 minutes to install, slower than the median of the 51 comparable projects Argusic has measured.

Of the 52 cli projects Argusic has installed and timed, radian was the 50th fastest to reach a running state, and 47 of 52 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	2/3	Runs with mocks	92.00	0.23	2026-10-04 00:13 UTC
Argusic Runner	1/3	Ran out of time	0.00	0.19	2026-10-03 23:43 UTC

Topics (from GitHub)

cli console ipython r radian repl terminal

Embed the badge

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

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

Questions

Does radian run?: radian runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 28 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test radian?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 545f504f672d. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test radian?: The run that produced this verdict cost $0.23: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does radian take to install?: 28 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 radian need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing radian?: 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.
How does radian compare with the alternatives?: Of the 52 cli projects Argusic has installed and timed, radian was the 50th fastest to reach a running state, and 47 of 52 reached one at all.
Where is the evidence for radian?: 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.