RIP parses any repository into a knowledge graph with Tree-sitter. Works offline and no Docker required — Neo4j, Qdrant are optional for team/server use.
Install via pip in one command:
pip install repo-intelligence==0.1.0
Open a terminal, cd to your repository, and run repo init .
repo index . then start tracing functions! That's it!
No Docker, no servers, or network required. Works 100% offline.
Probes for Neo4j/Qdrant/Postgres; uses server providers if available.
Use all features: REST API, Flutter, Context Gateway, shared indexes.
Every query is answered from a real graph traversal or vector search — not an LLM guessing at file contents. The model only narrates what the graph already proved.
Every file, class, function and widget becomes a node. Calls, imports, and inheritance become typed edges in Neo4j.
trace · impact · dependenciesQdrant vector search finds code by what it does, not what it's named. Hybrid-ranked against the graph for precision.
vector + lexical + graph rerankShips as an MCP server. Claude Code, Cursor, and Codex call rip_trace instead of reading files blind.
Before you touch a symbol, know exactly what breaks. Risk-scored, graph-traversed, no guessing.
blast-radius before you commitPython, TypeScript, Java, Go, Rust, and Dart/Flutter — same graph schema, same query surface, every repo.
tree-sitter parsedNeo4j, Qdrant and Postgres on your machine or your server. Your code never has to leave the network.
docker compose upRemote Git indexing works from terminal and the Flutter APK. Clone any repo into a named folder, then index only the subfolder you care about.
RIP can now clone a GitHub repository from the CLI or Flutter APK, initialize the selected project folder, respect .gitignore, and keep that project isolated from every other indexed repo.
Use an explicit clone folder and a subfolder target. For Flutter apps, indexing lib keeps the graph focused on application code instead of Android, iOS, and build scaffolding.
repo git-index https://github.com/pratiksingh1702/flutter_music_app.git --folder-name flutter_music_app_lib --project-name flutter_music_app_lib --subdir lib --branch main
The mobile app exposes the same flow through chat and the Add Repository sheet: Git URL, clone folder, index subfolder, project name, and branch all map to the same backend job.
/index https://github.com/pratiksingh1702/flutter_music_app.git --folder flutter_music_app_lib --project-name flutter_music_app_lib --subdir lib --branch main
Remote clone jobs run Git in a worker thread, avoiding Windows event-loop subprocess failures under Uvicorn reload.
The clone folder stores the repository, while the indexed root can be a subfolder such as lib. Project IDs are derived from that indexed path.
Git-backed discovery uses tracked plus untracked non-ignored files, so ignored build output does not enter the graph.
WebSocket and polling status report clone path, index path, subfolder, files indexed, entities found, and actionable failures.
Tree-sitter builds an exact AST per file. No regex guessing.
Entities and relationships land in Neo4j as typed nodes and edges.
Code chunks are vectorized into Qdrant for semantic recall.
CLI, REST, MCP, or mobile — same graph, same answers.
RIP is MIT-licensed and has no roadmap decided behind closed doors. Every graph query, every parser, every line of the Context Gateway is there for you to read, fork, or improve.
Tree-sitter grammars exist for 100+ languages. The parser interface is small and documented — C#, Kotlin, and Ruby are open.
good first PR · core/parser/The Context Gateway's scoring weights are hand-tuned, not learned. If you have ideas on better relevance signals, this is the highest-leverage area.
help wanted · gateway/core/ranker/Real-world repos surface real-world bugs. Index something messy and file what broke — that's the most valuable signal we get.
report issues · no code requiredMost of the codebase has no written walkthrough beyond inline comments. If you read code to understand it, that's a doc gap to fix.
docs/ · no setup neededThe REST API and MCP server are stable interfaces. A web dashboard, a JetBrains plugin, an Obsidian integration — bring your own frontend.
server/ · mcp/ · stable contractsNo published numbers exist yet comparing RIP against grep, plain RAG, or other code-intelligence tools. First measured benchmark gets credited.
scripts/benchmark.shStandard GitHub fork workflow. uv sync and you're running locally in minutes.
Labelled good first issue or help wanted if you want a starting point.
Small, focused changes merge fast. Tests and a one-line rationale go a long way.
No Discord yet — issues and discussions live on GitHub where the code already is.
Open source. Self-hosted. No telemetry leaving your machine.