walk
Terminal file manager
Runssource: GitHubGoMITcommit bf802ef9ee4b
Go, MIT licensed. The project labels itself: cli, file manager and terminal.
walk runs. An Argusic agent installed it in 19.7 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
walk v1.13.0 builds from source with Go, passes all 2 tests (TestFileSize, TestFileMode), and the pre-built binary can be downloaded via install.sh.
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.
- V compiler (vlang) installed unnecessarily - this is a Go project, not a V project10 minutes
- The V compiler from master branch had broken cached .vh headers preventing self-compilation5 minutes
- No TTY available to run the interactive terminal app2 minutes
- Install time
- 20 minutes
- Cold machine to finish
- 15 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- `go test -v ./...` exited 0: TestFileSize PASS, TestFileMode PASS. `go build` produced a working binary that reports `v1.13.0`. The binary panics on `/dev/tty` (expected in headless CI), proving it's a real executable.
- Model tokens used
- 231,466
- Exact commit tested
- bf802ef9ee4b
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 0ms: -rwxrwxr-x 1 runner runner 11500013 Nov 9 10:30 /home/runner/bin/walk v1.13.0 Let me compute the total time and provide the results. exec /bin/sh -lc 'date +%s' in /work/repo succeeded in 0ms: 1794220247 Started around 1794219064, now 1794220247 = ~19.7 minutes. Let me compile the final report. tokens used 231,466 Started around 1794219064, now 1794220247 = ~19.7 minutes. Let me compile the final report.
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 3 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 19.7 minutes to install, slower than the median of the 123 comparable projects Argusic has measured.
Of the 124 cli projects Argusic has installed and timed, walk was the 117th fastest to reach a running state, and 112 of 124 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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/walk)Questions
- Does walk run?
- Yes. walk runs. Argusic installed and launched it on a clean machine in 20 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test walk?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit bf802ef9ee4b. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test walk?
- The run that produced this verdict cost $0.22: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does walk take to install?
- 19.7 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 walk need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing walk?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does walk compare with the alternatives?
- Of the 124 cli projects Argusic has installed and timed, walk was the 117th fastest to reach a running state, and 112 of 124 reached one at all.
- Where is the evidence for walk?
- 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.