What is Repowise?
Repowise is an open-source, evidence-backed codebase intelligence platform and Model Context Protocol (MCP) server engineered to solve the context inefficiency of autonomous coding agents. Instead of forcing agents like Claude Code, Cursor, Codex, or Windsurf to repeatedly grep, read, and rediscover codebase relationships on every prompt, Repowise pre-indexes abstract syntax trees (ASTs), dependency graphs, git co-change history, test reachability, and architectural decisions into a continuously updated local index. In empirical benchmarks, Repowise reduces coding agent output by 31.6% and shrinks retrieval context payloads by up to 97.2% (from 13,984 down to 393 tokens) while running completely locally with zero LLM API dependencies for its core graph analysis.
Key Features & Technical Capabilities
- Universal Codebase Dependency Graph: Constructs file- and symbol-level dependency graphs across 26 AST-parsed programming languages. Delivers confidence-stamped call resolution, community clustering, centrality scores, and execution flow tracking.
- Ten Task-Shaped MCP Tools (
dev.repowise/repowise): Specifically designed around developer workflows rather than low-level data entities. Agents can query blast radius, caller graphs, and architectural context across multiple targets in a single MCP round trip. - Zero-LLM Deterministic Engine: Dependency graphing, change risk scoring, test impact analysis, dead code identification, and code health scans run entirely on local CPU cycles without sending source code to external LLM providers or incurring API costs.
- Intelligent Command Distillation (
repowise distill): Pre-processes noisy shell and test runner outputs (e.g.pytest,git log) before the agent reads them, eliminating 60% to 90% of irrelevant log tokens while preserving reversible reference anchors ([repowise#<ref>]). - 51-Detector Code Health Scoring: Evaluates codebases on a 1–10 scale across defect risk, maintainability, and cross-functional performance bottlenecks (such as cross-file N+1 queries). Calibrated against empirical defect corpora, surfacing 2.3× more defects than CodeScene under identical review budgets.
- Symbol-Level Blast Radius & Change Risk: Evaluates pull request diffs on a 0–10 risk scale based on commit shapes, modified contracts, and historical bug magnets. Automatically determines the exact test subset exercised by a diff.
- Automated PR Bot (GitHub App): Adds a single, self-updating PR comment highlighting symbol-level contract modifications, outside callers, missing co-change companion files, and a visual blast-radius treemap.
- Local Visual Dashboard (
repowise serve): Hosts an interactive local web UI featuring explorable dependency architecture graphs, interactive code-health heatmaps, natural language codebase chat, and auto-generated wiki documentation.
Benchmark: Repowise vs. Unassisted Agent Retrieval
| Evaluation Dimension | Unassisted Agent (Grep / Read Loop) | Repowise-Indexed Agent | Measured Improvement |
|---|---|---|---|
| Agent Tool Calls (Django Suite, n=43) | 7.2 tool calls | 3.8 tool calls | −31.6% agent output (p<0.0001) |
| Commit Context Payload | 13,984 tokens | 393 tokens | 97.2% context reduction |
| Defect Identification vs. CodeScene | Baseline (CodeScene 1.0×) | 2.3× defect capture | 130% higher defect yield (p=0.003) |
| Test Impact Precision (Reachability) | 72.1% (one-hop import heuristic) | 95.7% precision (100% hit rate) | +23.6% precision gain |
| Core Analysis LLM Token Cost | Variable per prompt | $0.00 (Zero LLM calls) | Deterministic local compute |
CLI Quickstart & Usage
Install Repowise via PyPI and initialize your repository index in under two minutes:
# Install from PyPI
pip install repowise
# Initialize local codebase index (no API key required)
cd /path/to/your/project
repowise init --no-prose -y
# Start local web dashboard and MCP server
repowise serve
Inspect change risk and run impact-focused test suites before merging:
# Assess change risk on current branch against main
repowise risk main..HEAD
# Run only the test files directly exercised by the diff
repowise impacted-tests main..HEAD
# Distill test output to eliminate token waste for AI agents
repowise distill pytest
# View accumulated token and cost savings
repowise saved
Claude Code & MCP Integration
To connect Repowise to Claude Code, Cursor, or any Model Context Protocol host, configure your .mcp.json or Claude configuration file:
{
"mcpServers": {
"repowise": {
"command": "repowise",
"args": ["mcp"],
"env": {}
}
}
}
Technical Specifications
| Core Framework | Python / Tree-sitter / SQLite (Local Storage) |
|---|---|
| Supported Languages | 26 AST-parsed languages (Python, TypeScript, Rust, Go, Java, C++, etc.) |
| MCP Identifier | dev.repowise/repowise |
| License | Open Source (AGPL-3.0) / Commercial available |
| Integrations | Claude Code, Codex, Cursor, VS Code, GitHub Actions, GitHub App |
| External Dependencies | None (Zero cloud services required for core graph analysis) |
| Official Repository | github.com/repowise-dev/repowise |
| Official Website | https://www.repowise.dev |
| Documentation | https://docs.repowise.dev |
Frequently Asked Questions
How does Repowise reduce token consumption and agent costs?
Instead of having coding agents crawl whole files or search directories repeatedly, Repowise pre-computes dependency graphs and supplies precise symbol-level context. Combined with output distillation (repowise distill), agents avoid ingesting repetitive compiler or test logs, cutting task token payloads by up to 97.2%.
Does Repowise upload proprietary source code to external servers?
No. Repowise is fully self-hosted. All AST parsing, git analysis, change-risk calculations, and code-health scoring execute locally on your machine or private CI infrastructure without requiring any external LLM API key.
How does Repowise identify impacted tests without coverage reports?
Repowise traverses the static call and import graph to determine which test files reach modified source symbols. In empirical benchmarks against real coverage runs, this approach achieves 95.7% precision and a 100% hit rate, ensuring only affected tests are executed.
Which IDEs and agent hosts support Repowise?
Repowise natively integrates via the Model Context Protocol (MCP) with Claude Code, Cursor, Windsurf, Codex, and VS Code. It also provides automatic CLAUDE.md and AGENTS.md generator hooks for non-MCP agents.