xerj
XERJ is the new way for AI to search data. Its autoindex capability activates agents to know your data without the token waste of grep and sed. One command indexes code, docs, logs and PDFs for search, RAG, security audits and agent memory, using 40x fewer tokens than grep. Elasticsearch compatible, so existing clients just work.
Runssource: GitHubhomepageRustApache-2.0commit fa27e936272c
Rust, Apache-2.0 licensed. The project labels itself: ai search, ai search algorithms, ai search engine, ai search free, ai search module, ai search optimization, ai searchengine and bm25 search.
xerj runs. An Argusic agent installed it in 3 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
xerj v1.0.0-rc.77 is installed at /home/runner/.local/bin/xerj, started in 690ms on --insecure mode, successfully autoindexed /work/repo/docs (18 datasets, 9681 records, 21s wall time), and serves queries on http://127.0.0.1:9200 with ES 8.13 wire protocol. No build step needed (binary install from GitHub releases). Field report filed at user-feedback/16-agent-field-reports/2026-10-03-autoindex-query-field-report.md.
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.
- Install time
- 3 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- xerj --version returned 'xerj v1.0.0-rc.77'; curl -s http://127.0.0.1:9200/ returned 200 with ES 8.13-compatible JSON; xerj autoindex /work/repo/docs indexed 285 files as 2934 records across 18 datasets in 21s wall time; curl search on ax-docs for 'architecture' returned 43 hits with correct BM25 scoring; xerj search and xerj autoindex map both produced correct output
- Model tokens used
- 57,696
- Exact commit tested
- fa27e936272c
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Now let me stop the server and do a final check of the xerj binary.
exec
/bin/sh -lc '# Kill the server, this was just for testing
kill $(ps aux | grep '"'xerj --insecure' | grep -v grep | awk '{print "'$2}'"') 2>/dev/null; echo \…
# Final check on the binary
export PATH=\"/home/runner/.local/bin:"'$PATH" && xerj --version 2>&1 && echo "---" && file /home/r…
exited 127 in 0ms:
done
xerj v1.0.0-rc.77
/bin/sh: 5: file: not found
tokens used
57,696Replay 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.
- Installed in 3 minutes.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 3 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
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)
ai-searchai-search-algorithmsai-search-engineai-search-freeai-search-moduleai-search-optimizationai-searchenginebm25-searchelastic-searchelasticsearchelasticstackgraph-searchgraph-semantic-searchhybrid-searchhybrid-semantic-searchsearch-apisearch-enginesemantic-searchvector-databasevector-search
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/xerj)Questions
- Does xerj run?
- Yes. xerj runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test xerj?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit fa27e936272c. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test xerj?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does xerj take to install?
- 3 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 xerj need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing xerj?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for xerj?
- 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.