iocraft

A Rust crate for beautiful, artisanally crafted CLIs, TUIs, and text-based IO.

Runssource: GitHubhomepageRustApache-2.0commit 7eae7583da91

Rust, Apache-2.0 licensed. The project labels itself: cli, iocraft, logs, rust, terminal and tui.

iocraft runs. An Argusic agent installed it in 3 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The iocraft Rust workspace builds and all 151 tests pass (139 iocraft lib + 12 macros) when NO_COLOR is unset; the hello_world and borders examples produce correctly formatted terminal output with styled borders and text.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
2
last tested
stars
1,586
forks
71
open issues
28
watchers
4
size
6 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 iocraft, 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.

  • rustc not found — Rust toolchain missing from container0.7 minutes
  • 4 iocraft tests failed with NO_COLOR=1 set in container env — color_output_disabled() suppresses SGR sequences, causing SgrColor::to_string() to emit empty strings and crossterm backend to skip color ansi codes, breaking assertions0.3 minutes
Install time
3 minutes
Cold machine to finish
3 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
NO_COLOR= cargo test -p iocraft --lib: 139 passed, 0 failed; NO_COLOR= cargo test -p iocraft-macros: 12 passed (1 unit + 11 doc-tests), 0 failed; NO_COLOR= cargo run --example hello_world: printed 'Hello, world!' with rounded border; NO_COLOR= cargo run --example borders: rendered 4 border-style boxes correctly
Model tokens used
28,182
Exact commit tested
7eae7583da91
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.

Session started around Mon Nov 18 16:00:00 UTC 2024
exec
/bin/sh -lc 'echo "Current time: $(date)" && . "$HOME/.cargo/env" && cd /work/repo && echo "Repo ti…
 succeeded in 0ms:
Current time: Sat Nov 14 16:19:10 UTC 2026
Repo timestamp: 1794672971
Here's the final result:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 3, "er…
tokens used
28,182
Here's the final result:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 3, "er…

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 3 minutes.
  • 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 Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 127 cli projects Argusic has installed and timed, iocraft was the 63rd fastest to reach a running state, and 115 of 127 reached one at all.

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 3 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.02
Argusic Runner1/3Runs100.000.11

Topics (from GitHub)

cliiocraftlogsrustterminaltui

Embed the badge

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

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

Questions

Does iocraft run?
Yes. iocraft runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test iocraft?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7eae7583da91. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test iocraft?
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 iocraft take to install?
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 iocraft need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing iocraft?
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.
How does iocraft compare with the alternatives?
Of the 127 cli projects Argusic has installed and timed, iocraft was the 63rd fastest to reach a running state, and 115 of 127 reached one at all.
Where is the evidence for iocraft?
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.

Discussion