inquire
A Rust library for building interactive prompts
Runssource: GitHubhomepageRustMITcommit 3d5b65422a24
Rust, MIT licensed. The project labels itself: cli, command line, interactive, prompt, rust, terminal and tui.
inquire runs. An Argusic agent installed it in 35 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
inquire 0.9.4 Rust workspace compiles with rustc 1.82.0, all 250 tests pass when NO_COLOR is unset, all 3 workspace crates (inquire, inquire-derive, examples) build successfully.
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 60 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.
- [email protected] requires rustc >= 1.82 (transitive via rstest)10 minutes
- Rust toolchain not installed5 minutes
- rust-std component incomplete3 minutes
- Disk space exhausted (3 Rust tarballs + build artifacts)3 minutes
- cargo binary missing from rustc install2 minutes
- [email protected] requires rustc >= 1.812 minutes
- Install time
- 35 minutes
- Cold machine to finish
- 33 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- NO_COLOR= cargo test: 183 lib tests, 12 derive tests, 55 doc-tests = 250 passed, 0 failed, 1 ignored
- Model tokens used
- 167,666
- Exact commit tested
- 3d5b65422a24
- 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.
**Fixed dependency version issues** - `[email protected]` required rustc 1.81+; downgraded to 2.0.0 via `cargo update` - `[email protected]` (transitive via `rstest`/`toml_edit`) required rustc 1.82+; upgraded to Rust 1.… **Fixed test environment** - `NO_COLOR=1` was set in the container environment, which made crossterm suppress all ANSI color s… **Disk space** was exhausted by 3 Rust tarball copies + the build cache; ran `cargo clean` to recov… **Final verification** — `cargo test` (with NO_COLOR unset): - `inquire` lib: 183 tests passed, 0 failed - `inquire-derive` lib: 3 tests passed, 0 failed - `inquire-derive` integration: 9 tests passed, 0 failed - `inquire` doc-tests: 55 tests passed, 0 failed - Total: **250 passed, 0 failed, 1 ignored**
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.
- Recovered from all 7 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.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 35 minutes to install, slower than the median of the 49 comparable projects Argusic has measured.
Of the 50 cli projects Argusic has installed and timed, inquire was the 49th fastest to reach a running state, and 46 of 50 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.
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 | 100.00 | 0.09 | |
| Argusic Runner | 1/3 | Did not run | 20.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/inquire)Questions
- Does inquire run?
- Yes. inquire runs. Argusic installed and launched it on a clean machine in 35 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test inquire?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3d5b65422a24. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test inquire?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does inquire take to install?
- 35 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 inquire need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing inquire?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does inquire compare with the alternatives?
- Of the 50 cli projects Argusic has installed and timed, inquire was the 49th fastest to reach a running state, and 46 of 50 reached one at all.
- Where is the evidence for inquire?
- 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.