
ivygrep
io.github.bvolpatoPublished by GitHub account bvolpatov1.3.1Updated Oct 29, 2026
Local code search and task context packs for coding agents
Overview
Local code and notes search server that gives coding agents ranked hits and token-budgeted context packs from your own repositories.
- What you can do
- Search code and notes by natural-language intent, exact literal, symbol, references or callers, with path, language and glob filters
- Build context packs for a coding task from the task text, pasted paths and staged, uncommitted or branch changes since a Git ref, trimmed to a token budget
- Index repositories and note directories locally, with a daemon that keeps the index current as files change
- Return ranked file paths, line numbers, previews and a reason for each selected evidence item, plus warnings for partial failures
- When to use it
- Useful when a coding agent should look things up in a local repository or notes folder before broad filesystem scans, and when you want implementation context assembled from code relationships and recent changes rather than raw file dumps.
- Requirements
- Runs as a local process on the user's machine (desktop only), installed via Homebrew, WinGet, a release installer or a source build; the MCP entry launches the ig binary with the --mcp flag. No account or API key is declared. The default neural model downloads pinned assets on first use; the hash tier avoids model downloads. Git is optional but needed for --since change context.
Installation
In SourceWeft
- Open ivygrep in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Search code and notes. Build context for coding tasks.
Files and queries stay on your machine. The default model downloads its pinned assets on first use.
[CI] [Security] [Relevance] [Latest release] [MIT license]
[ivygrep search followed by a bounded task-context pack]
Website · Architecture · Benchmarks · Contributing · Discussions
Search and build context
Abridged output:
Search returns ranked file paths, line numbers, and previews. Context packs add related code and explain why each item was selected.
The context command uses your task, file paths in pasted text, and staged or uncommitted changes.
With --since, it resolves the selected ref and finds its Git merge base with
HEAD. The pack includes changes committed on the current branch since that
base, plus staged, unstaged, and untracked files. The selected ref does not act
as the diff base itself.
Deleted changes can contribute Git history labeled git_deleted to a context
pack. The unreleased deletion fix excludes missing files from current search results.
The pack can include definitions, callers, dependencies, tests, configuration, and documentation.
It trims the rendered Markdown to the requested estimated token budget. It does not generate an answer or modify files.
Use --since main, --since HEAD~3, or --since '@{upstream}' inside a Git worktree.
For a directory without Git, omit --since.
Install
Installers select a compatible archive, verify its SHA-256 checksum, and install ig.
The shell installer selects a Metal build on Apple Silicon. It selects CUDA
only on Linux x86_64 when an NVIDIA GPU with compute capability 8.0 or newer is
visible and the CUDA 13 runtime is available. Other supported hosts use the
portable build. Homebrew installs the Metal build on Apple Silicon and portable
builds on Intel macOS and Linux. CUDA and Metal accelerate optional transformer
profiles; the default model runs on CPU in every build.
Run ig hardware to check compatibility and see the matching reinstall command.
Build from source on macOS or Linux:
Search
The first query indexes the current repository. The daemon then watches for changes and updates the index incrementally.
Starting with v1.3.1, search immediately excludes a file that the safe file reader confirms is missing, even before watcher reconciliation. Reconciliation then removes entries owned by that workspace. Permission, unavailable, and symlink failures are not treated as deletion. Earlier releases retain the indexed-text fallback for missing files.
Linked Git worktrees share a base index. An overlay tombstone hides a base-backed file deleted on that branch without changing what other worktrees can search. Deleting a file added only in the worktree removes its overlay entries and does not need a base tombstone.
Useful controls include -n for result files, -C for context lines, --type
for language, --include/--exclude path globs, --lexical-only, --hash, and --json. --hash
uses lightweight local embeddings for faster startup and no model download,
with lower semantic quality. Run ig --help for full reference.
Literal search ranks files by matching lines. A bounded search shows up to three previews per file and reports omitted matches. Use --no-limit to return every match, or --file-name-only to return paths without building previews.
Standalone uppercase AND, OR, and NOT are Boolean operators.
For example, ig "settings NOT render" excludes results that contain render.
Short malformed expressions, such as a trailing OR, return an error.
If an invalid Boolean query spans multiple lines or has at least 13 words, ivygrep searches it as plain text.
The results include a warning. The CLI writes it to stderr. MCP and the Web UI return it in warnings.
Valid Boolean expressions keep their Boolean meaning, including in long prompts.
To search operator words as text, use lowercase letters or wrap the words in backticks or quotes.
Multi-line queries that read as pasted source rank the code that contains the snippet above one-line
definition signatures that share a few of its identifiers. Multi-paragraph prompts, pasted issue text,
and questions with a blank line rank as prose, with signature matches scored like body text. For pasted
error output, such as a traceback, a Caused by: chain, or a panicked at line, lexical, path,
hash-vector, and reranking signals ignore runtime values such as paths outside the workspace, ids, and
timestamps, and the static message text is matched against the code that raises it. Neural query vectors
still embed the original text.
On macOS laptops, background neural enhancement pauses on battery power (ig --status
shows Paused: Battery Power); set IVYGREP_ENHANCE_ON_BATTERY=1 to keep it running.
The lightweight hash tier keeps computing on battery so semantic results stay available.
However many workspaces change at once, at most two hash and two neural enhancement
workers run at a time (IVYGREP_ENHANCE_MAX_WORKERS); the rest wait in the daemon, and the
workspace searched or edited last goes first.
Search notes and memories
Index notes once. Watcher keeps them current, and queries use local semantic + lexical search by default:
Public MemoryQuest results (v1.2.7): 74.9% recall@20 at 87.63 ms warm p95. Benchmark measures retrieval only; answer accuracy is outside scope.
Connect coding agents
Codex and Claude Code packages install MCP configuration plus focused task-context skill:
Automatic setup detects the client, preserves existing configuration, writes the absolute ig path, verifies the MCP handshake, and runs a search:
Restart an open client after installation. Manual MCP setup is also available:
Cursor .cursor/mcp.json:
OpenCode opencode.json:
Agents call ig_search for discovery. Set output=context_pack and budget_tokens=8000 when the task needs implementation context. Pass the absolute path to the active repository or worktree. Worktrees reuse the base index and store only changed chunks and tombstones.
Context packs can include definitions, callers, references, dependencies, dependents, tests, configuration, and docs.
Setup guides: Codex, Claude Code, Cursor, Gemini CLI, OpenCode, and MCP.
Recommended agent instruction:
How it works
- A Git-aware walker finds changed or indexable files.
- Tree-sitter and bounded text fallbacks produce structural chunks.
- SQLite stores metadata and relationships. Tantivy stores lexical postings. USearch stores hash vectors and model vectors.
- Query routing runs bounded exact, lexical, symbol, hash, and optional neural passes before fusion.
- Context expands primary hits through code relationships and recent changes, then trims rendered evidence to requested token budget.
Fresh indexing publishes lexical results before vector enhancement. Worktrees reuse base index and store only divergent chunks and tombstones. Partial workspace failures return warnings with valid hits; complete failure errors.
ivygrep supports 45 language and file types. Twenty-four use Tree-sitter AST chunking: Rust, Python, Go, JavaScript, TypeScript, Java, C, C++, C#, Kotlin, Scala, PHP, Ruby, Swift, Elixir, Zig, Bash, Haskell, OCaml, Lua, Dart, Objective-C, Perl, and Starlark.
Read architecture for storage, commit order, retrieval, worktrees, protocols, security boundaries, and module ownership.
System performance
The historical v1.2.7 benchmark used a deterministic synthetic corpus with one million chunks. Across three hash-only trials, median warm CLI p95 was 6.19 ms. Controlled indexing reached 150,576 chunks/s. The final index used 0.42 GiB. These results measure scale and footprint, not retrieval quality or coding-task accuracy. They do not describe the current neural model under concurrent load.
The resource and latency report measures the released binary with both static model profiles. It includes repeated enhancement measurements, forced-neural p99, eight MCP clients, RSS, CPU, and disk writes. The model-screening report remains separate because it used one repetition.
Historical scale measurements (v1.2.7) · Million-chunk methodology · Full benchmark dashboard
The source implementation limits cached results to 64 MiB and cached neural queries to 4 MiB. Parsed context input has a shared 32 MiB cache. Content digests prevent reuse after a file changes. Idle search contexts share a 256 MiB estimated budget. Each index run has a 32 MiB estimated budget for queued payloads. A large file can exceed the indexing target when it runs alone. These budgets do not cap total process RSS. See memory budgets and diagnostics for scope and timing commands.
Local and private
Runtime source, queries, embeddings, results, and indexes stay local. Neural
profiles download pinned model assets on first use unless cache is already
populated. Use --hash, ./build.sh --hash-only, or
cargo build --locked --no-default-features to avoid model downloads.
ig --web binds to loopback by default. Its Web API requires a session token, including on loopback.
The printed URL contains that token. Keep terminal output and logs that capture it private.
The browser opens through an owner-only redirect file in the app home. This keeps the token out of process arguments.
To skip the browser, set IVYGREP_NO_BROWSER=1.
Non-loopback listeners use plain HTTP. Use a trusted network, Tailscale, or an encrypted tunnel. Never expose the listener directly to the internet. Indexed file contents can appear in snippets. This includes dotfiles that your ignore rules permit.
Report vulnerabilities through a private security advisory. Release archives include checksums, SBOMs, and provenance.
Data and configuration
Indexes and daemon state live in ~/.local/share/ivygrep on every OS (under %USERPROFILE% on Windows).
IVYGREP_HOME overrides that path; otherwise a non-empty XDG_DATA_HOME selects $XDG_DATA_HOME/ivygrep.
Model assets use the Hugging Face cache (HF_HOME, default ~/.cache/huggingface), which other tools may share.
There is no configuration file. Use CLI flags and the environment variables.
Starting with v1.3.1, a CLI search or context request, ig --interactive, or
ig --add prompts before it builds an index for your home directory, a
directory containing it, or the filesystem root. Confirm with y or yes.
Without an interactive terminal, the command stops unless you pass --yes.
An already indexed, healthy directory does not prompt on a plain ig --add.
ig --add --force rebuilds it, and --skip-gitignore may add ignored files,
so those cases prompt too.
The daemon also removes the index of a directory that stays missing for seven days (IVYGREP_INDEX_GC_GRACE_SECS), and the overlay of a worktree removed with git worktree remove after ten minutes.
Troubleshooting, upgrade, and uninstall
Open the URL ig --web prints: a bare http://127.0.0.1:4747/ returns 401 until
the browser has the session cookie that URL sets.
If ig --web opens a page that cannot load its redirect file, as snap-packaged
browsers on Ubuntu do for files under hidden directories, open the URL it prints.
Under WSL, a Windows browser can load the redirect file only through an opener
that translates Linux paths, such as wslview; otherwise open the printed URL.
Upgrade through the channel you installed from: brew upgrade ivygrep,
winget upgrade --id BrunoVolpato.ivygrep --exact, or rerun the installer. The
next command restarts a daemon from an older build; index format changes rebuild
existing indexes once on first use.
To uninstall, run brew uninstall ivygrep or winget uninstall --id BrunoVolpato.ivygrep --exact,
or delete ig from the installer directory (~/.local/bin or %LOCALAPPDATA%\ivygrep\bin unless
IVYGREP_INSTALL_DIR was set). Then stop any running ig --daemon process and delete the data directory.
Contribute
Start with a good first issue, read CONTRIBUTING.md and architecture, or discuss an idea in Discussions.
MIT licensed. Maintained by Bruno Volpato.
Source: README.md at commit 3a379ec
Tools
0Version history
3- v1.3.1LatestOct 29, 2026
- v1.3.0Sep 26, 2026
- v1.2.16Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts