🔍 unumsearch
The detective for your code. Your AI agents search the same files all day; unumsearch keeps the clues.
接入你的智能体
從發布者安裝。不是 PlugMCP 端點。
遠端 URL 還是本機指令? 兩種安裝方式的差異
An AI coding agent asks the same kind of question hundreds of times a day: where is this
function called? which files mention that setting? A plain search like rg answers by reading
every file, every time. Over dozens of checkouts that is gigabytes per question.
unumsearch works like a detective with a good notebook. It keeps a compact index of clues: every 3-letter piece of text and the files it appears in. A question becomes a set of clues, the index names the few suspect files that hold all of them, and only those are opened and checked line by line against the real file. Same answer as ripgrep, usually in milliseconds.

Live run, real timings: 12 search patterns our agents actually issued, over ~180 agent worktrees
(258k files), one engine at a time with a warm page cache. Nothing is replayed or sped up. Run it on
your own code with python3 bench/race.py --root . (see it yourself).

fresh..gitignore, hidden files,
binaries and size cap)..ssh/, .aws/, .env*, *.key, *.pem, secrets.json and
other credential files are never indexed, whatever the configuration says.20 regexes mined from a week of real coding-agent tool calls, on the author's machine (2026-10-09). Honest notes:
rpc). A new CLI process per query is slower than rg on a small
repository (12 ms vs 9.8 ms)..env.example files, which unumsearch never indexes on purpose.git checkout rewrites 44,686 Linux kernel files, the index has caught
up 6.4 to 7.5 s after the checkout began; until then answers say fresh: false, so an agent
can fall back to its own scan. 0 of 64,454 fresh answers differed from ripgrep.Method, every table and the weak spots: docs/BENCHMARKS.md. What is guaranteed and how it is tested: RELIABILITY.md.
curl -fsSL https://github.com/corpunum/unumsearch/releases/latest/download/install.sh | sh
irm https://github.com/corpunum/unumsearch/releases/latest/download/install.ps1 | iex
unumsearch --root ~/src/myrepo index # build the index once
unumsearch search 'fn\s+main' ~/src/myrepo --text # ask a question
unumsearch --root ~/src/myrepo serve # keep it fresh + serve the local API
Static binaries for Linux (x86_64, aarch64), macOS (arm64, x86_64) and Windows (x86_64), each
verified against SHA256SUMS with a build-provenance attestation. Config file, systemd unit and
building from source: Reference → Install.
Checked, per-tool setup: docs/integrations.
Every answer is JSON with backend (index/scan), covered, fresh, truncated and
complete, so a client knows exactly when to trust it and when to scan itself. Inside: per-unit
trigram shards with delta/varint postings and a next-byte mask, a regex-to-trigram planner, and
incremental rebuilds that re-read only changed files. Details: Reference → How it works.
.ssh, .gnupg, .aws, .config, .kube, .env*, keys,
credential files), from any front-end.Host headers.auth_token / UNUMSEARCH_TOKEN).Full list: Reference → Security.
Reference (every option, API, FAQ) · Benchmarks · Reliability · Integrations · Changelog · Agent Skill
Apache-2.0 (includes the MPL-2.0 nucleo-matcher dependency) · built by corpunum · sibling project:
UnumPingPong (AI agents rally on your tasks; a referee decides who scores)
Fast, agnostic indexed file & code search engine in Rust: CLI, daemon, MCP server, agent skill, library
工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
這筆記錄未列出必要的環境變數。
Unumsearch 透過 stdio 在本機執行。
上次檢查時間:2026-11-16。 Fast, agnostic indexed file & code search engine in Rust: CLI, daemon, MCP server, agent skill, library