CodeScry is a local codebase retrieval tool for coding agents. It indexes committed code from local git repos into a local SQLite database, then exposes ranked snippets through a CLI and MCP stdio server.
Why CodeScry
- Local-first by default: auto-selects local Ollama
mxbai-embed-largewhen available, otherwise falls back to hash embeddings and SQLite storage. - Agent-ready: MCP tools for
search_code,get_symbol,list_repos, andreindex. - Large-index aware: bounded sqlite-vec candidate paths avoid scoring every chunk once vectors are backfilled.
- Semantic opt-in: Ollama, OpenAI, and sentence-transformers providers are available when quality matters more than default speed.
- Measured on real repos: public agent-natural evals and ranking/performance findings live in
docs/ranking-experiment-findings.md.
Recent private ~/code mxbai eval improved from ~20.7s average query latency to ~1.8s after filtered vector serving optimizations, with Recall@10 stable at 0.800. See docs/performance.md for knobs and diagnostics.
Install
Fast path:
curl -LsSf https://raw.githubusercontent.com/Zhachory1/codescry/main/scripts/install.sh | sh
The installer uses uv tool install codescry when uv is available, otherwise pipx install codescry. If neither uv nor pipx is installed, it bootstraps pipx with python3 -m pip --user.
If you prefer explicit installs:
pipx install codescry
# or, if uv is already installed
uv tool install codescry
Node users can run the npm wrapper after installing uv:
npx codescry doctor
The npm package is a thin wrapper around the Python package. It does not bundle local SQLite index data.
For development:
python -m venv .venv
source .venv/bin/activate
pip install -e '.[dev]'
Check local readiness:
codescry doctor
First success path
For a deterministic five-minute smoke test, see docs/getting-started.md.
Index this repo or another local git repo:
codescry index /path/to/git/repo
Query it:
codescry query "where is request retry handled" -k 5
Lookup a symbol:
codescry get-symbol RepoIndex --repo /path/to/git/repo
Discover and index every git repo under a root:
codescry index-root ~/code
Show indexed repos and freshness:
codescry status
MCP setup
Run the MCP server over stdio:
codescry serve
Agent config example:
{
"mcpServers": {
"codescry": {
"type": "stdio",
"command": "/Users/YOU/.local/bin/codescry",
"args": ["--db", "/Users/YOU/.codescry/index.sqlite", "serve"],
"env": {}
}
}
}
npm/npx config example:
{
"mcpServers": {
"codescry": {
"type": "stdio",
"command": "npx",
"args": ["-y", "codescry", "--db", "/Users/YOU/.codescry/index.sqlite", "serve"],
"env": {}
}
}
}
Use which codescry to find the absolute command path for your machine when using direct CLI installs.
Freshness hooks
Install hooks for one repo or a repo root:
codescry install-hooks /path/to/git/repo
codescry install-hooks ~/code --recursive
Hooks run best-effort after commit/merge:
codescry --db <db> reindex "$PWD"
They preserve the selected DB path and must not fail git commands.
Docs
docs/getting-started.md— install to first useful query.docs/mcp-clients.md— MCP config examples.docs/troubleshooting.md— common setup/query/freshness issues.docs/cli-reference.md— command reference.docs/output-schema.md— JSON fields.docs/evals.md— eval authoring and gate.docs/performance.md— query/index latency knobs, candidate union, batching, and debug telemetry.docs/embedding-providers.md— hash, Ollama, OpenAI, and sentence-transformers embedding providers.docs/pilot.md— 5-engineer pilot measurement plan and local reporting commands.docs/language-support.md— parser/regex/window support matrix.docs/recipes.md— common operations.docs/upgrade-uninstall.md— lifecycle commands.docs/release.md— PyPI-first and npm-wrapper release flow.docs/ranking-experiment-findings.md— retrieval/ranking experiments and eval findings.
Evals
The seed golden set lives in evals/golden.codescry.jsonl.
Run the eval gate:
codescry eval evals/golden.codescry.jsonl . -k 10 --fail-under 0.85
Pilot proof
Pilot task/activation/miss events are recorded in ~/.codescry/usage.jsonl without snippets. Passive query logging is opt-in with CODESCRY_ENABLE_USAGE_LOG=1. Use:
codescry pilot report
See docs/pilot.md for activation, timing, miss capture, and decision gates.
Retrieval behavior
- Default
autoembeddings use local Ollamamxbai-embed-largewhen available, otherwise local deterministic hash vectors. - Optional embedding providers include Ollama, OpenAI, and sentence-transformers. See
docs/embedding-providers.md. - Changing embedding provider or model requires reindexing because stored vectors are model-specific.
- Python functions/classes/methods get parser-backed symbol metadata.
- TS/JS/Go/Java/Rust/C/C++/SQL get Tree-sitter parser-backed symbol metadata.
- Other common declaration patterns get regex-backed symbol metadata.
get_symboluses stored symbol metadata before search fallback.- Search blends vector, lexical, symbol, and path scores.
- Results include stale/dirty flags.
Data boundary and safety
- Default
autoprovider does not use hosted APIs. It uses local Ollama if available, otherwise local hash embeddings. - Default configuration does not send source code to hosted external APIs.
- OpenAI and non-local Ollama embedding endpoints send chunks and queries outside your machine. See
SECURITY.mdanddocs/embedding-providers.md. - Index data is local SQLite derived data and can be deleted/rebuilt.
- Files matching high-confidence secret patterns are skipped and prior chunks for those paths are removed.
- Secret skipping is a best-effort local guardrail, not a guarantee. See
SECURITY.md.
Current limits
- Python uses stdlib AST parser chunks; TS/JS/Go/Java/Rust/C/C++/SQL use Tree-sitter parser chunks; other languages use regex-backed symbol hints plus line windows.
- Default
autoembeddings prefer local semantic Ollama when available and fall back to hash embeddings otherwise; hosted semantic embeddings are opt-in only. - SQLite remains the default local store; large-index serving uses bounded sqlite-vec candidate paths where vector coverage exists.
- Freshness is committed-code freshness; dirty working-tree edits are reported but not indexed.
Metadata
Release files for codescry 0.3.6
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 | |
|---|---|---|---|---|
| codescry-0.3.6.tar.gz | 90.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| codescry-0.3.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 144.3 kB
Release files / codescry-0.3.6.tar.gz
| Download URL | codescry-0.3.6.tar.gz |
|---|---|
| Size | 90.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a6bd9dc63e3c2c1ec1cfb3056ff08ded22e12a38c9e9763a284d5214c4b2f71e
|
|
BLAKE2b-256 checksum How to use checksums |
b5a3e2c9e9e18e8a2c70d16a568db3c35dcdb908c348a0a07d5fe2ceaa20c2c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.17 {"installer":{"name":"uv","version":"0.9.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / codescry-0.3.6-py3-none-any.whl
| Download URL | codescry-0.3.6-py3-none-any.whl |
|---|---|
| Size | 53.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
296804af1e57fa74bf5b8a2241c7b371bf773149b8eaf2d052d4183e72b19fd8
|
|
BLAKE2b-256 checksum How to use checksums |
3355ddfd15afd00fb2318150549324f522e163257751d73f7e678dc0ab0617ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.17 {"installer":{"name":"uv","version":"0.9.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for codescry 0.3.6
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.