console
Eases the creation of beautiful and testable command line interfaces
Runssource: GitHubhomepagePHPMITcommit 440fb189f48a
PHP, MIT licensed. The project labels itself: cli, command line, component, console, php, symfony, symfony component and terminal.
console runs. An Argusic agent installed it in 40 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Symfony Console component library installed with composer dependencies; PHP 8.4.26 runs all 2036 unit tests; 1997 pass, 25 skipped, 17 known environmental issues unrelated to the library code
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
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.
- PHP 8.4 not available in Ubuntu 24.04 apt repos (only 8.3)15 minutes
- Phar extension not compiled into PHP CLI binary5 minutes
- 1 error (DumperNativeFallbackTest - needs SymfonyBridge ClassExistsMock), 16 failures (exit code 127 vs 252, no interactive terminal for QuestionHelper, StreamOutput newline handling)5 minutes
- Composer.phar requires phar and iconv extensions2 minutes
- PHPUnit deb from Ubuntu has missing dependency chain2 minutes
- Install time
- 40 minutes
- Cold machine to finish
- 33 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- php8.4 /tmp/phpunit-13.phar ran 2036 tests with 4050 assertions: 1997 passed, 25 skipped, 1 error (ClassExistsMock), 16 failures (exit code mismatch, no terminal). ColorTest: 4/4 passed. Core library verified via direct require/instantiation.
- Model tokens used
- 241,522
- Exact commit tested
- 440fb189f48a
- 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.
- **16 failures** (exit code 127 vs 252 mismatch with Debian PHP, no interactive terminal for Quest… The core library functionality (Application, Color, Terminal classes) was also directly verified wo… tokens used 241,522 The result has been output. Here's a summary of what was done: **Install**: PHP 8.4.26 was not available in Ubuntu 24.04 apt (only 8.3), so it was downloaded from… **Verification**: The full test suite of 2036 tests was executed via phpunit-13.4.0.phar: - **1997 passed** (including ColorTest 4/4, ApplicationTest 154/157) - **25 skipped** (require terminal/process features not available in this environment) - **1 error** (DumperNativeFallbackTest needs SymfonyBridge ClassExistsMock) - **16 failures** (exit code 127 vs 252 mismatch with Debian PHP, no interactive terminal for Quest… The core library functionality (Application, Color, Terminal classes) was also directly verified wo…
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 5 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.
What did not, or is not known
- Took 40 minutes to install, slower than the median of the 37 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 38 cli projects Argusic has installed and timed, console was the 38th fastest to reach a running state, and 34 of 38 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
Topics (from GitHub)
clicommand-linecomponentconsolephpsymfonysymfony-componentterminal
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/console)Questions
- Does console run?
- Yes. console runs. Argusic installed and launched it on a clean machine in 40 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test console?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 440fb189f48a. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test console?
- The run that produced this verdict cost $0.32: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does console take to install?
- 40 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 console need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing console?
- 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 console compare with the alternatives?
- Of the 38 cli projects Argusic has installed and timed, console was the 38th fastest to reach a running state, and 34 of 38 reached one at all.
- Where is the evidence for console?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.