{"id":115406,"date":"2026-09-03T01:08:21","date_gmt":"2026-09-03T01:08:21","guid":{"rendered":"https:\/\/youzum.net\/qwen-developers-open-sources-zg-zvec-grep-a-local-first-search-layer-unifying-ripgrep-bm25-and-vector-search\/"},"modified":"2026-09-03T01:08:21","modified_gmt":"2026-09-03T01:08:21","slug":"qwen-developers-open-sources-zg-zvec-grep-a-local-first-search-layer-unifying-ripgrep-bm25-and-vector-search","status":"publish","type":"post","link":"https:\/\/youzum.net\/de\/qwen-developers-open-sources-zg-zvec-grep-a-local-first-search-layer-unifying-ripgrep-bm25-and-vector-search\/","title":{"rendered":"Qwen Developers Open-Sources zg (zvec-grep): A Local-First Search Layer Unifying ripgrep, BM25, and Vector Search"},"content":{"rendered":"

Coding agents spend a large share of their tool budget on search. When the target is a known symbol, ripgrep<\/a> answers it exactly. When the target is a behavior described in plain language, keyword matching often misses, and the agent falls back to guessing terms, reading whole files, and assembling context by hand. Each of those detours costs tool calls, tokens, and wall-clock time.<\/p>\n

The Qwen Developer team announced<\/a> zg<\/strong> (zvec-grep), an open-source local-first search layer that puts semantic search, BM25, and ripgrep behind one interface for both humans and agents. The code ships under the zvec-ai GitHub organization<\/a> with an Apache 2.0 license.<\/p>\n

Is it deployable?<\/strong> Yes, today. It installs from npm as @zvec\/zvec-grep<\/code><\/a>, requires Node.js 22 or newer on macOS, Linux, or Windows, needs no GPU with the default model, and the Apache 2.0 license permits commercial use. <\/p>\n

One index, four retrieval routes<\/strong><\/h2>\n

zg indexes a workspace once and then exposes several ways to query it. The retrieval pipeline docs<\/a> define four routes: a hybrid default that combines intent with lexical anchors, --fts<\/code> for BM25-ranked exact terms, --vector<\/code> for conceptual similarity with no lexical ranking, and --rg<\/code> for exhaustive literal or regex matching. The first three read the index. The --rg<\/code> route needs no index at all, which matters when a repository has not been indexed yet.<\/p>\n

An anonymous workspace index lives in <root>\/.zvec-grep\/<\/code>. Both .git<\/code> and .zvec-grep<\/code> are always excluded, along with common dependency, build, cache, and log directories, plus anything the repository\u2019s own ignore rules exclude. Re-running zg index<\/code> updates incrementally; changing the embedding model requires an explicit --rebuild<\/code> because vector spaces from different models are incompatible even at matching dimensions.<\/p>\n

Indexed results report a freshness state of fresh<\/code> or possibly_stale<\/code>, so an agent can act on a good-enough result instead of running a status preflight first.<\/p>\n

The MCP surface agents actually see<\/strong><\/h2>\n

zg install<\/code> detects Codex, Claude Code, Cursor, and OpenCode on the machine and wires up the local MCP integration. The server speaks Streamable HTTP MCP on a loopback-only endpoint at http:\/\/127.0.0.1:7999\/mcp<\/code>, with optional bearer authentication.<\/p>\n

The design decision worth noting is restraint. Per the MCP guide<\/a>, the default agent<\/code> toolset exposes exactly two tools: zvec_grep_search<\/code> for when the intent is known but the exact string is not, and zvec_grep_rg<\/code> for when a symbol, path, or regex is known. Index lifecycle stays with the CLI. A six-tool compatibility set that adds index create, drop, status, and server status exists but is opt-in through zg server on --mcp-toolset full<\/code>, and the docs state that an agent must never silently create, rebuild, or delete a persistent index.<\/p>\n

Output is shaped for context economy. Results come back grouped by file with line spans, and indexed source previews are omitted by default unless requested. zg also rejects output-changing ripgrep flags such as --json<\/code>, --count<\/code>, -l<\/code>, and --vimgrep<\/code> so the compact result format holds.<\/p>\n

Embeddings run on device by default<\/strong><\/h2>\n

The embedding catalog<\/a> currently documents ten local models and three remote Qwen endpoints. The quickstart default, local\/potion-code-16m-v2<\/code>, is a Model2Vec static model with a 256-dimension output and an 8,192-token input limit; because it uses static vector lookup, selecting a GPU does not speed it up. Heavier local options include jina-embeddings-v2-base-code<\/code>, embeddinggemma-300m<\/code>, and qwen3-embedding-0.6b<\/code>. Remote options run to qwen\/qwen3.7-text-embedding<\/code> at 128,000 input tokens and the multimodal qwen\/qwen3-vl-embedding<\/code>.<\/p>\n

Remote use is gated. Configuring a provider credential does not authorize data transfer; that requires either --allow-remote<\/code> for a single command or a signed workspace grant via zg auth grant<\/code>, revocable with zg auth revoke<\/code>. The launch post cites eleven on-device models against ten in the current docs, a small discrepancy worth flagging.<\/p>\n

What the benchmark numbers say<\/strong><\/h2>\n

The evaluation numbers appear in the launch post, not in the repository, where the benchmarks section is still a placeholder. Both runs were paired A\/B tests holding agent, model, prompt, runtime, and task constraints fixed, with the zg condition adding only a prebuilt index, MCP tools, and usage guidance. Index build cost is excluded from the tables.<\/p>\n

On a 20-question SWE-QA-Bench sample, zg cut tool calls by more than half and input tokens by nearly half while raising the Judge score by 1.50 points. On an 80-question BrowseComp-Plus sample, accuracy moved from 98.67% to 99.00% while input tokens fell 37.56%, tool calls 43.52%, and agent time 38.58%. Separately, indexing the Django repository (3,457 files) is reported to finish in under 30 seconds on an Apple M4 Pro.<\/p>\n

Sample sizes of 20 and 80 questions are small, and the reported reductions come from the vendor\u2019s own runs, so independent replication is the obvious next step.<\/p>\n

Interactive explainer<\/strong><\/h2>\n
\n<\/div>\n

\n

Key Takeaways<\/strong><\/h2>\n