yt-fts runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 1 minutes, hitting 7 errors on the way, and recorded the session.

How did Argusic test yt-fts?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7fbc0088f306. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test yt-fts?

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

How long does yt-fts take to install?

1 minute 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-fts need a GPU?

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

What goes wrong when installing yt-fts?

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.

Where is the evidence for yt-fts?

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.

yt-fts

YouTube Full Text Search - Search all of YouTube from the command line

Runs with mockssource: GitHubPythonUnlicensecommit 7fbc0088f306

Python, Unlicense licensed. The project labels itself: chromadb, cli, click, full text search, llm, rag, semantic search and sqlite.

yt-fts runs, with stand-ins for the services it depends on. An Argusic agent installed it in 1 minute and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The yt-fts Python package installs via virtual env, CLI responds to --version/--help/config, list and full-text search work against the downloadable test database, and all 9 tests pass after patching download mocks and API-key mocks.
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 92 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs with mocks
Argusic Score: 92 / 100
cost of the verifying run: $0.23 (measured)
recorded runs: 1
last tested: 2026-10-05
stars: 1,811
forks: 97
open issues: 13
watchers: 10
size: 0 MB
created: 2023-05-20
last push: 2026-01-22

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-05. 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 yt-fts, 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.

test_download.py used real yt-dlp calls which fail because YouTube changed channel layout; downloads yield 0 videos8 minutes
vsearch/export_vsearch tests required real API keys for OpenAI/Gemini embeddings3 minutes
test_search.py did not load test database before tests; tests failed with no such table: Channels1 minute
test_search.py::test_global_search asserted YC Root Access which does not exist in test DB1 minute
test_export.py used subprocess.run("rm *.csv") without -f, crashing when no csvs existed1 minute
test_download.py populate_jcs_channel referenced undefined loop variable i1 minute

Install time: 1 minutes
Cold machine to finish: 19 minutes
Errors hit and fixed: 7 hit, 7 fixed with no human help
How the result was proved: pytest tests/ exited 0, 9 passed, 0 failed; yt-fts --version prints yt_fts version: 0.1.62; yt-fts list and yt-fts search return correct data against pre-loaded test database downloaded from yt-fts-testdb-server
Model tokens used: 224,406
Exact commit tested: 7fbc0088f306
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
Behaviour against real services: this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

    ],
    'test_depth': 'tier2_mock',
    'notes': 'yt-dlp download integration broken against real YouTube due to API changes; download …
    'verified_how': 'pytest tests/ exited 0, 9 passed, 0 failed; yt-fts --version prints yt_fts ver…
    'final_state': 'The yt-fts Python package installs via virtual env, CLI responds to --version/-…
}
print(json.dumps(r))
\"" in /work/repo
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 1, "errors": [{"msg": "tes…
tokens used
224,406

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

Installed in 1 minute.
Recovered from all 7 errors without a human stepping in, which says the failures are documented well enough to solve.
Licensed Unlicense, as reported by its host.

What did not, or is not known

Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
Measured once so far. A single attempt shows it can run, not that it runs reliably.

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	1/3	Runs with mocks	92.00	0.23	2026-10-05 19:35 UTC

Topics (from GitHub)

chromadb cli click full-text-search llm rag semantic-search sqlite youtube yt-dlp

Embed the badge

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

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

Questions

Does yt-fts run?: yt-fts runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 1 minutes, hitting 7 errors on the way, and recorded the session.
How did Argusic test yt-fts?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7fbc0088f306. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test yt-fts?: The run that produced this verdict cost $0.23: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does yt-fts take to install?: 1 minute 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-fts need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing yt-fts?: 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.
Where is the evidence for yt-fts?: 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.