Local Codebase Indexer
A local codebase indexer and context provider for AI coding assistants (Claude Code via MCP, GitHub Copilot / Codex via CLI). It helps them navigate large legacy codebases with far fewer tokens. Everything is stored in .ai_context/indexer.db inside your project, with no cloud services involved. The design follows index.md.
Install
pip install local-codebase-indexer # Python 3.10+
# or, isolated from your other packages:
pipx install local-codebase-indexer
# optional real embeddings (see below): pip install "local-codebase-indexer[onnx]"
From a clone: pip install -e . (the bin/indexer launcher still works in a checkout).
For AI assistants
If you are an AI coding assistant asked to set this up: run pip install local-codebase-indexer, then claude mcp add local-indexer -- local-codebase-indexer --root <project> serve (Claude Code) or use the CLI commands below. Full instructions are in AGENTS.md.
Usage (CLI)
local-codebase-indexer --root <project> index # build / incrementally refresh the index (--force rebuilds all)
local-codebase-indexer search "database mapping for LotNo" --limit 5
local-codebase-indexer relations IExistOpenHandleService --direction both # upstream | downstream | both
local-codebase-indexer context Services/LotService.cs --lines 120 --padding 15 # alias: slice
local-codebase-indexer data-access MES_Lot # who reads / writes / executes a table or procedure; what a procedure touches
local-codebase-indexer stats
local-codebase-indexer status # is the index fresh? failed files, git commit, consistency checks
- Without
--rootthe current directory is used;INDEXER_ROOTalso works. - Put
--jsonbefore the subcommand to get JSON output. search,relationsandcontextrun an incremental refresh first (mtime check, then md5 only when mtime changed).- The tool names from the spec also work as subcommands:
codebase_semantic_search,codebase_get_symbol_relations,codebase_get_optimized_context(options--query,--symbol_name --relation_direction,--file_path --focus_lines --padding_lines).
Usage (Claude Code / MCP)
claude mcp add local-indexer -- local-codebase-indexer --root /path/to/project serve
# without installing: claude mcp add local-indexer -- uvx local-codebase-indexer --root /path/to/project serve
serve speaks JSON-RPC (MCP) over stdio and exposes five tools: codebase_semantic_search, codebase_get_symbol_relations, codebase_get_optimized_context, codebase_get_data_access, codebase_index_status.
Three-layer index
| Layer | Implementation |
|---|---|
| Syntactic | tree-sitter for C#, Python, JavaScript, TypeScript/TSX; regex for SQL (PROCEDURE / VIEW / FUNCTION / TABLE); other text files (VB6 .frm, .config, .md, ...) are split into windowed chunks |
| Topology | using / import resolved to file dependencies, inheritance (base lists) and type usage (invocation), stored in the dependencies table |
| Semantic | 384-dim chunk embeddings in vss_chunks; queries fuse FTS5 keyword, symbol-name and vector rankings with Reciprocal Rank Fusion, then expand to the dependency neighbours of the top 3 files |
Encodings: UTF-8 first, then Big5, then cp1252. Files over 5MB are skipped. Root and nested .gitignore files are respected, and .git, bin, obj, node_modules and similar directories are always skipped.
Differences from the spec
- Vector storage:
sqlite-vssneeds a native extension and is no longer maintained, sovss_chunksstores float32 BLOBs and cosine similarity is computed with numpy. No extension to install. - Embedding model: the default is a built-in hashing embedder (identifier sub-words, bigrams, CJK character bigrams). It is fast and reproducible but does not understand synonyms. For real transformer embeddings, export
all-MiniLM-L6-v2orbge-small-en-v1.5to ONNX, installonnxruntimeandtokenizers, and setINDEXER_ONNX_MODEL=<folder with model.onnx and tokenizer.json>(the loading, padding, pooling and re-index logic is covered by a test with a tiny synthetic model; retrieval quality with a real model has not been measured, so runpython benchmarks/run_benchmark.py --compare benchmarks/baseline.jsonwith the variable set to check it; mean pooling suits MiniLM, bge models recommend CLS pooling). Switching embedders triggers a full re-index. - Call relations for C# are resolved with limited type inference (using / namespaces, field and constructor-injected types, locals, interface to implementation), and every edge carries a confidence:
confirmed(the receiver type is known),probable(reached through an interface or a single candidate) orcandidate(name match only). There is no Roslyn: no overload resolution by argument type, no delegates / lambdas / extension methods, and call chains are followed one level. Inheritance edges come from the AST and are reliable. - Extra schema additions:
symbols.qualified_name,chunk_metadata.symbol_id, and theraw_refs,chunks_ftsandmetatables.
Data access (SQL)
data-access <table-or-procedure> answers "what writes / reads / executes X". It is built from T-SQL (INSERT / UPDATE / DELETE / MERGE / TRUNCATE / SELECT INTO / FROM / JOIN / EXEC, with alias resolution; CTEs, temp tables and system objects excluded), from C# SQL strings (literals, +, interpolation, string.Format, consts, locals) passed to Dapper, SqlCommand or EF FromSql, from stored-procedure names used with CommandType.StoredProcedure, and from EF ToTable / [Table] mappings. A procedure's callers are indirect writers of the tables it writes (followed up to 4 hops). Each entry has a confidence; dynamic SQL (EXEC(@sql), sp_executesql, SQL built from unknown values) cannot be resolved and is listed separately as uncertain, never mixed into the confirmed lists. Known gaps: FROM a JOIN b ON ..., c loses c, and a stored-procedure name passed to a non-database method is not seen.
Natural-language search routes questions such as "who modifies MES_ScrapRecord" or "哪些程式會寫入 MES_Lot" to this index first.
Query expansion
Queries are expanded with a small synonym dictionary (SP / 預存程序 / stored procedure / usp, table, lot, scrap, ...; local_codebase_indexer/synonyms.py). Add or disable groups per project in .ai_context/synonyms.json: {"groups": [["wpnlot", "在製批"]], "disable": ["sp"]}. This helps abbreviations and Chinese/English terms, not free paraphrase.
Index health
status (also the MCP tool codebase_index_status) reports whether the index can be trusted without refreshing it: fresh, stale (files changed or git HEAD moved since the last update), degraded (failed files or an inconsistent database) or not_indexed. A file that fails to parse is removed from the index, listed with its error, and retried on every update, so search never returns stale lines for it. index --force rebuilds everything.
Benchmark
python benchmarks/run_benchmark.py measures Recall@5, Recall@10 and MRR on fixed queries. See benchmarks/README.md.
Tests
python -m pytest -q
Metadata
Release files for local-codebase-indexer 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| local_codebase_indexer-0.2.1.tar.gz | 92.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| local_codebase_indexer-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 154.1 kB
Release files / local_codebase_indexer-0.2.1.tar.gz
| Download URL | local_codebase_indexer-0.2.1.tar.gz |
|---|---|
| Size | 92.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2945513f9322aa6d9f327e0dd3a9fc13a784d86aaf84b31dd3388d797f494c2d
|
|
BLAKE2b-256 checksum How to use checksums |
d47ece0793d8f60aeade0f99b60e224e2c3d28942db60742305a5f54e63beac9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logRelease files / local_codebase_indexer-0.2.1-py3-none-any.whl
| Download URL | local_codebase_indexer-0.2.1-py3-none-any.whl |
|---|---|
| Size | 61.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
870a5e2ea5cca73358e2c7cb2dcefc569faebdee07468b586cae137dcf3ce530
|
|
BLAKE2b-256 checksum How to use checksums |
ea558f96830448cbc77811558cf7fd91dd5c65172d547b660a4c182cb081e6a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logSecurity for local-codebase-indexer 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for local_codebase_indexer-0.2.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.