
Codeintel
io.github.phuongddxPublished by GitHub account phuongddxv0.4.0Updated Oct 24, 2026
Local-first SCIP code navigation and Zoekt search over your own indexed repositories
Overview
Local-first code intelligence that lets an assistant navigate indexed repositories with exact symbol references, definitions, call hierarchies and lexical code
- What you can do
- jarvis precomputes a local code-intelligence layer over your own indexed repositories so an assistant can query symbols instead of grepping. It exposes ten MCP tools, including findReferences for exact occurrences, goToDefinition for defining ranges, callHierarchy and typeHierarchy for relationships, documentSymbols for file outlines, searchCode for Zoekt lexical or regex search, blastRadius for cross-repo package dependents, getIndexStatus for freshness, and indexRepo to build an index (R4, R46-R56). Indexing is explicit and the query path is read-only (R64, R70).
- When to use it
- Use it when a coding agent repeatedly greps a repository and burns context filtering comments, tests and similarly named symbols from real hits (R1-R3, R6). It suits questions such as where a symbol is used, where it is defined, or what calls it, answered from precomputed indexes rather than by opening every match (R7, R18). It is retrieval only, so renames and refactors are out of scope (R63).
- Requirements
- macOS arm64/x86_64 or Linux arm64/x86_64 only; Windows is not supported (R60). Install the standalone Homebrew binary, which embeds Python 3.12 and the needed tooling, so no Python, uv, pip or PyPI install is required (R12, R14); Linux needs Homebrew/Linuxbrew first (R11). Register the local stdio server, for example jarvis-server, and use its absolute path if the client cannot find it on PATH (R17, R19, R20). Optional per-language indexers need Node.js/npm, a JDK, Xcode or a modern Bash (R28-R-
Installation
In SourceWeft
- Open Codeintel 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
jarvis
[CI] [Platforms] [License: MIT] [MCP]
Your coding agent should not spend its context window on grep.
When your agent asks "where is AuthService used?", grep returns comments,
markdown, test fixtures, and similarly named symbols in one noisy pile. The
agent burns context re-reading files to filter signal from noise — and still
misses call sites.
jarvis precomputes a local code-intelligence layer so your agent calls
findReferences for exact occurrences, goToDefinition for the defining
range, callHierarchy for call paths, and searchCode for precise lexical
search — ten MCP tools for Claude Code, Cursor, or any MCP client.
Your code and indexes never leave your machine.
[grep returns noisy results vs jarvis findReferences returning 10 exact file:line:col occurrences]
Quick start · MCP tools · Dashboard · Limits · Details · Docs
Quick start
1. Install the standalone binary:
Linux users need Homebrew/Linuxbrew
installed first. The formula supports macOS arm64/x86_64 and Linux
arm64/x86_64, installs both jarvis and jarvis-server, and embeds Python
3.12, dashboard assets, tree-sitter libraries, watch, scip,
zoekt-git-index, and zoekt-webserver. Homebrew supplies
universal-ctags. No Python, uv, pip, or PyPI installation is required.
Upgrade with brew upgrade jarvis; recover a damaged installation with
brew reinstall jarvis.
2. Index a repo (slug defaults to the directory name):
3. Register the MCP server:
Ask your agent "find all references to AuthService" — it calls
findReferences instead of grepping.
Other MCP clients (Cursor, Claude Desktop, any stdio client)
If your client can't find jarvis-server on PATH (GUI apps often don't
inherit your shell's), use the absolute path from which jarvis-server.
Claude Code plugin (registers MCP + ships agent skills)
Install the Homebrew binary first. The plugin adds jarvis skills and can
register the already-installed jarvis-server.
Optional language indexers
The standalone package includes the SCIP converter and both Zoekt binaries.
The Homebrew formula does not install setup.sh; from a jarvis source
checkout, install the optional per-language indexer for your repo:
For Maven-built Java repositories on macOS, also install a modern Bash with
brew install bash, then run sh setup.sh --only bash-shim from that same
source checkout. Reindex after adding an indexer. Without the matching
indexer, documentSymbols and goToDefinition still work via Tree-sitter
where coverage exists;
findReferences, callHierarchy, and typeHierarchy return recovery
guidance.
Not included
semanticSearch is registered for MCP compatibility but is excluded from the
standalone distribution. It returns a Homebrew-specific unavailability error
that points to the source-build steps below; lexical search and symbol search
remain available.
Source-build semantic search
The standalone Homebrew package excludes semantic dependencies. In a source checkout, install them with:
Then index explicitly:
install-semantic also pre-downloads the embedding model (BAAI/bge-m3,
~4.3 GB, one time) into the shared Hugging Face cache
(~/.cache/huggingface/); every indexed repo reuses it. If the download is
interrupted, the next jarvis index retries it automatically.
MCP tools
Dashboard
A localhost web console over the same ~/.jarvis data the CLI and MCP server read:
[Repositories view] [Tool playground]
Requirements and limits
- macOS arm64/x86_64 and Linux arm64/x86_64 only. Windows is not supported.
- Semantic search is unavailable in the Homebrew distribution.
- One language per repo — detected by extension plurality across git-tracked files; override with
--language. - jarvis never edits code. It is the retrieval half — Serena complements it for renames/refactors.
- Indexing is explicit — run
jarvis index(orjarvis watch) before querying.
Details
How it works
One indexing CLI writes precomputed indexes into ~/.jarvis; one stdio
runtime reads them down. The two share no other contract.
- Publishing is atomic — a reindex writes a new snapshot, then flips the
currentpointer viaos.replace. A query reading the old snapshot keeps working; no downtime window. - The runtime path never writes — every query opens the published snapshot read-only (
mode=ro&immutable=1). - The package graph is rebuilt, not accumulated — each reindex clears that repo's outgoing edges before recomputing.
Full detail: docs/system-architecture.md
Indexing CLI reference
Known upstream limitations
scip-javacan't index Android/Gradle repos — its Gradle plugin keys off standard source sets that AGP replaces (scip-java#177). Detected automatically; degrades to search-only.- Kotlin indexing requires an exact Kotlin version match —
scip-kotlincis compiled against one pinned release (currently2.2.0). Detected automatically. - Maven-built Java repos need bash ≥ 4.4 on macOS —
brew install bashfixes it. - Swift indexing requires
scip >= v0.9.0— older converters silently drop occurrence ranges.jarvis indexrefuses an oldersciprather than publishing a broken index.
Configuration
The source-development semantic path has additional model-prefix overrides; they have no effect in the standalone distribution.
Documentation
docs/project-overview-pdr.md— scope, value prop, out-of-scope itemsdocs/system-architecture.md— architectural guarantees, storage layout, query pathsdocs/codebase-summary.md— module map, test coveragedocs/code-standards.md— code patterns and conventionsdocs/dashboard.md— dashboard views, actions, security model
License
Source: README.md at commit 4cf9176
Tools
0Version history
1- v0.4.0LatestSep 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