SearchCLI
Open CLI for integrating AI search, recommendation, and conversational retrieval into agent systems and business systems
Runs with mockssource: GitHubTypeScriptApache-2.0commit 2d757a9cb783
TypeScript, Apache-2.0 licensed. The project labels itself: agent tools, ai agents, ai search, ai search engine, automation, cli, command line tool and conversational search.
SearchCLI runs, with stand-ins for the services it depends on. An Argusic agent installed it in 2 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
SearchCLI installs with Node.js 20.18.0, builds from TypeScript to dist/, and passes all 55 acceptance tests including auth import-env, skill list/show, search tune plan/run/apply, v2 dataset lifecycle onboarding (8-step pipeline with mock HTTP server), and CLI help/version commands.
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
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.
- Node.js v18.19.1 in container does not meet the >=20 requirement0.5 minutes
- Install time
- 2 minutes
- Cold machine to finish
- 2 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- node ./scripts/run-acceptance.cjs --dist --suite all exited 0, 55 passed (26 core + 29 v2-onboarding), all using built-in mock server
- Model tokens used
- 36,869
- Exact commit tested
- 2d757a9cb783
- 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.
Let me verify the accepted time spent: exec /bin/sh -lc 'echo "Started at: $(TZ=UTC date -d @$(stat -c %Y /work/repo/package.json))" && echo "C… succeeded in 0ms: Started at: Wed Nov 18 13:17:26 UTC 2026 Current: Wed Nov 18 13:19:28 UTC 2026 Total elapsed time is about 2 minutes from the start of the container (13:17:26) to now (13:19:28).… Here is the final result: tokens used 36,869 Total elapsed time is about 2 minutes from the start of the container (13:17:26) to now (13:19:28).… Here is the final result:
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 2 minutes, faster than the median of the 6 comparable projects Argusic has measured.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
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.
Of the 7 agent-tools projects Argusic has installed and timed, SearchCLI was the 2nd fastest to reach a running state, and 4 of 7 reached one at all.
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 with mocks | 92.00 | 0.03 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.02 |
Topics (from GitHub)
agent-toolsai-agentsai-searchai-search-engineautomationclicommand-line-toolconversational-searchinformation-retrievalragrecommendationrecommendation-systemretrievalsearch-clisearch-enginesemantic-searchtypescriptvolcengine
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/searchcli)Questions
- Does SearchCLI run?
- SearchCLI runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test SearchCLI?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2d757a9cb783. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test SearchCLI?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does SearchCLI take to install?
- 2 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 SearchCLI need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing SearchCLI?
- 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 SearchCLI compare with the alternatives?
- Of the 7 agent-tools projects Argusic has installed and timed, SearchCLI was the 2nd fastest to reach a running state, and 4 of 7 reached one at all.
- Where is the evidence for SearchCLI?
- 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.