chimera find
Search a repository by what code DOES, not by the string it contains. `chimera/rag/` has been in the tree since 0.44.0 — symbol-level chunking over Python's AST, one SQLite file with an FTS5 index, RRF fusion — measured, documented, and reachable from nothing. A library with no entrance is a library nobody has. This is the entrance. Keyword by default; `--semantic` fuses it with embeddings, and the fusion is what was measured and adopted in `bench/rag/RESULTS.md`: hybrid 0.5050 against keyword 0.4425 on this repository, +6.25 pp paired over 400 probes, McNemar p = 1.7e-04. **`--semantic` means HYBRID, never vectors alone**, and that is the measurement rather than a preference: the vector arm on its own scored **0.4100 — worse than keyword**. Every point of the win comes from fusing two rankings that are wrong about different things. A flag that gave you the vector arm would be a flag that made your search worse. The recall figure is printed with every search because it is per-corpus and per-embedder: the same harness measures 0.4750 on this repository as it stood three weeks ago, and there is no conversion from one embedding model's vector space to another's.
Arguments
QUERYstrrequiredWhat you are looking for, in words.
Options
--pathstrdefault:'.'Repository to search.
--kintdefault:8How many results.
--reindexbooleanRebuild the index before searching.
--semanticbooleanFuse keyword with embeddings. Costs money to index.