Yes. yazi runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 1 error on the way, and recorded the session.

How did Argusic test yazi?

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

What did it cost to test yazi?

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

How long does yazi take to install?

15 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 yazi need a GPU?

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

What goes wrong when installing yazi?

1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for yazi?

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

yazi

💥 Blazing fast terminal file manager written in Rust, based on async I/O.

Runssource: GitHub homepageRustMITcommit 5f901b886b14

Rust, MIT licensed. The project labels itself: android, asyncio, cli, command line, concurrency, cross platform, developer tools and file explorer.

yazi runs. An Argusic agent installed it in 15 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Yazi 26.9.1 builds from source with Rust 1.98.1, both the TUI file manager (yazi) and CLI (ya) binaries produce correct version output, the TUI launches and renders the file listing interactively, and the CLI executes subcommands without error.
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.07 (measured)
recorded runs: 3
last tested: 2026-09-21
stars: 42,346
forks: 1,022
open issues: 61
watchers: 103
size: 10 MB
created: 2023-07-08
last push: 2026-09-21

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-22. 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 yazi, 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.

Rust toolchain not installed in the container1 minute

Install time: 15 minutes
Cold machine to finish: 22 minutes
Errors hit and fixed: 1 hit, 1 fixed with no human help
How the result was proved: yazi --version returned 'Version: 26.9.1'; ya --version returned 'Version: 26.9.1'; yazi TUI launched under PTY showing file listing of /work/repo; ya env printed full system/config diagnostics; ya pkg install ran without error; cargo check + cargo clippy passed (1 minor warning)
Model tokens used: 89,458
Exact commit tested: 5f901b886b14
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 2026-09-03. 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.

exec
/bin/sh -lc '. "$HOME/.cargo/env" && /work/repo/target/debug/ya --version 2>&1' in /work/repo
 succeeded in 0ms:
Ya
    Version: 26.9.1 (5f901b8 2026-09-14)
    Debug  : true
    Triple : x86_64-unknown-linux-gnu (linux-x86_64)
    Rustc  : 1.98.1 (48a229ce 2026-09-01)
All verified. Here's the final report:
tokens used
89,458
All verified. Here's 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 1 error 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 3 times, so the result is not a one-off.

What did not, or is not known

Took 15 minutes to install, slower than the median of the 7 comparable projects Argusic has measured.

Of the 8 android projects Argusic has installed and timed, yazi was the 8th fastest to reach a running state, and 7 of 8 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	3/3	Ran out of time	0.00	0.11	2026-09-21 14:43 UTC
Argusic Runner	2/3	Runs	100.00	0.07	2026-09-14 13:38 UTC
Argusic Runner	1/3	Runs	100.00	0.09	2026-09-03 11:33 UTC

Topics (from GitHub)

android asyncio cli command-line concurrency cross-platform developer-tools file-explorer file-manager filesystem linux macos neovim productivity rust terminal tui vim windows

Embed the badge

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

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

Questions

Does yazi run?: Yes. yazi runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test yazi?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5f901b886b14. 3 attempts are recorded, and the full method is on the methodology page.
What did it cost to test yazi?: The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does yazi take to install?: 15 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 yazi need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing yazi?: 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does yazi compare with the alternatives?: Of the 8 android projects Argusic has installed and timed, yazi was the 8th fastest to reach a running state, and 7 of 8 reached one at all.
Where is the evidence for yazi?: All 3 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.