yt-x
Posix script to browse youtube plus other yt-dlp supported sites from your terminal (fzf) or app launcher (rofi) with optional previews. (supports bash, zsh and dash)
Runssource: GitHubShellMITcommit d7e30982ae13
Shell, MIT licensed. The project labels itself: bash, cli, curl, dash, fzf, gum, jq and mpv.
yt-x runs. An Argusic agent installed it in 16 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
yt-dlp 2026.10.26, fzf 0.62.0, jq 1.7 installed. yt-x 0.8.7 script patched for fzf compatibility (wrap-word -> wrap; removed unsupported toggle binds). Config auto-generated at ~/.config/yt-x/config. Script prints version, help, completions, desktop entry, and successfully invokes yt-dlp to fetch YouTube search results.
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 96 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.
- fzf 0.62.0 removed --wrap-word, --preview-window=...,wrap-word option, and toggle-preview-wrap/toggle-wrap bind actions that yt-x 0.8.7 default config uses8 minutes
- Install time
- 16 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- yt-dlp --dump-single-json --flat-playlist --playlist-start 1 --playlist-end 3 https://youtube.com/results?search_query=test returned 3 entries; /work/repo/yt-x --version printed 'yt-x v0.8.7'; /work/repo/yt-x --cmd-exit -s test showed 'Loading...' and successfully fetched data via yt-dlp then opened fzf (blocked by no TTY)
- Model tokens used
- 373,038
- Exact commit tested
- d7e30982ae13
- 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: Config wrap options: --bind=ctrl-/:toggle-preview --preview-window=border-rounded,left,35%,wrap --wrap-sign='' --wrap" Script size: 170860 bytes Script hash: 51278ca27f006a5c00b21f87ac2a2b99d1ba8632626577a7b56b1bda6dd888d9 Here is the final report: tokens used 373,038 Here is 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 2 times, so the result is not a one-off.
What did not, or is not known
- Took 16 minutes to install, slower than the median of the 11 comparable projects Argusic has measured.
Of the 12 bash projects Argusic has installed and timed, yt-x was the 11th fastest to reach a running state, and 9 of 12 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.20 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.07 |
Topics (from GitHub)
bashclicurldashfzfgumjqmpvposixposix-compliantrofiscriptingterminaltuivlcyoutubeyt-dlpyt-dlp-wrapperyt-xzsh
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/yt-x)Questions
- Does yt-x run?
- Yes. yt-x runs. Argusic installed and launched it on a clean machine in 16 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test yt-x?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d7e30982ae13. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test yt-x?
- The run that produced this verdict cost $0.20: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does yt-x take to install?
- 16 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 yt-x need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing yt-x?
- 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 yt-x compare with the alternatives?
- Of the 12 bash projects Argusic has installed and timed, yt-x was the 11th fastest to reach a running state, and 9 of 12 reached one at all.
- Where is the evidence for yt-x?
- 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.