repowise

<!-- mcp-name: dev.repowise/repowise --> <div align="center">

<a href="https://www.repowise.dev"><img src=".github/assets/banner-v2.png" alt="repowise: evidence-backed codebase intelligence" width="100%" /></a>

<h1 align="center">Understand your codebase without paying your agent to rediscover it.</h1> <p align="center">Repowise indexes your code, dependency graph, git history, tests,<br /> documentation, and decisions once, then gives agents and developers cited answers,<br /> change impact, and concrete code-health fixes.</p> <p align="center"> <a href="https://www.repowise.dev"><img src="https://img.shields.io/badge/LIVE_DEMO-repowise.dev-F59520?style=for-the-badge&labelColor=0A0A0A" alt="Open the live Repowise demo" /></a> </p> <img src=".github/assets/product-map-dark.png" alt="Repowise connects code and dependency data, git history, tests and contracts, documentation, and architectural decisions in one continuously updated local index that gives developers and AI agents cited understanding, change impact, and concrete code-health improvements across editors, pull requests, dashboards, and multi-repository workspaces" width="100%" /> <table align="center"> <tr> <td align="center" width="250"><h2>−31.6%</h2></td> <td align="center" width="250"><h2>97.2%</h2></td> <td align="center" width="250"><h2>2.3×</h2></td> </tr> <tr> <td align="center" valign="top">_{<strong>less agent output</strong><br />3.8 vs 7.2 tool calls<br /><em>n=43 · p&lt;0.0001</em>}</td> <td align="center" valign="top">_{<strong>smaller context payload</strong><br />393 vs 13,984 tokens<br /><em>30 Flask commits</em>}</td> <td align="center" valign="top">_{<strong>more defects surfaced</strong><br />same 20%-of-lines budget<br /><em>2,770 files · p=0.003</em>}</td> </tr> </table> <p align="center">_{<strong>Graph accuracy leader at matched coverage.</strong><br /> No tool finding as much was more precise in all 7 compiler-graded cells.<br /> <em>5 tools · 37,853 oracle edges</em>}</p> <p align="center">_{<strong>Zero LLM calls</strong> for graph, risk, health, tests, dead code, and PR review. Generated prose is optional. Every benchmark publishes its sample, method, limitations, and losing rows.}</p> <p align="center">_{Free and self-hosted · core analysis stays on your infrastructure · no API key needed · AGPL-3.0 or commercial}</p> <p align="center"> <a href="https://repowise.dev/repo/repowise-dev/repowise"><img src="https://api.repowise.dev/badge/wiki/repowise-dev/repowise.svg?style=flat-square" alt="Explore Repowise's own code" /></a> <a href="https://repowise.dev/repo/repowise-dev/repowise/code-health"><img src="https://api.repowise.dev/badge/health/repowise-dev/repowise.svg?style=flat-square" alt="Repowise code health" /></a> <a href="https://pypi.org/project/repowise/"><img src="https://img.shields.io/pypi/v/repowise?style=flat-square&logo=pypi" alt="PyPI version" /></a> <a href="https://www.gnu.org/licenses/agpl-3.0"><img src="https://img.shields.io/badge/license-AGPL--3.0-059669?style=flat-square" alt="License: AGPL 3.0" /></a> </p> <p align="center"> <a href="#why-repowise"><strong>Why Repowise</strong></a> · <a href="#your-agent-stops-guessing"><strong>Agents</strong></a> · <a href="#know-whats-dangerous-before-you-merge"><strong>Changes</strong></a> · <a href="#code-health"><strong>Code health</strong></a> · <a href="#past-one-repo"><strong>Workspaces</strong></a> · <a href="#measured-against-the-field"><strong>Evidence</strong></a> · <a href="#for-teams-and-enterprises"><strong>Enterprise</strong></a> · <a href="https://docs.repowise.dev"><strong>Docs</strong></a> </p> </div>

---

<a id="why-repowise"></a>

One index. Three ways to use it.

| Understand the code | Change it safely | Improve it continuously | |---|---|---| | Ask cited questions · explore architecture and execution flows · read always-current docs · recover the decisions behind the code | See symbol-level blast radius · run only the tests a diff exercises · catch missing companion files · detect breaking contracts before merge | Find defect-prone files · separate maintainability from performance risk · remove dead code · hand concrete, graph-aware refactoring plans to an agent |

These are not disconnected scanners. The graph locates what git history flags; code health measures it; tests show what guards it; decisions explain why it exists; and the same evidence reaches your agent, editor, pull request, local dashboard, and cross-repository system map.

<div align="center"> <img src=".github/assets/demo.gif" alt="The Repowise dashboard running locally: health scores, the code-health map, a graph-aware refactoring plan, change coupling, and the generated documentation" width="100%" /> <p>_{A dashboard tour recorded on this repository. The same local index powers the UI, MCP tools, editor views, and PR analysis. No API key and nothing uploaded.}</p> </div>

Pick your front door

| If you care about… | Start here | |---|---| | A coding agent that understands the repository | Repowise finds the right files, returns task-shaped context in fewer calls, and proactively supplies decisions and risk. For agents ↓ | | Safer pull requests and faster test feedback | Get change risk, symbol-level callers, co-change partners, and a measured or graph-inferred test run list before merge. Change intelligence ↓ | | Finding and fixing the code most likely to hurt you | A defect-validated 1–10 health score across defect risk, maintainability, and performance, followed by the concrete refactoring plan. Code health ↓ | | Understanding an estate, not one repository | Match backend and frontend contracts, catch breaking providers, map downstream services, enforce architecture rules, and query every repo through one MCP endpoint. Workspaces ↓ | | Rolling this out across an engineering organization | Keep analysis on your infrastructure, give agents and reviewers the same evidence, and add commercial licensing, security controls, custom extensions, and SLA-backed support. Teams and enterprise ↓ |

<a id="quickstart"></a>

Start in minutes (no API key)

pip install repowise
cd /path/to/your/repo
repowise init --no-prose -y
repowise serve

That builds the graph, git, decisions, health, dead-code and structural-wiki layers locally. Connect Claude Code, Codex, Cursor or any MCP host, or open the dashboard. init wires Claude Code automatically. Then ask your agent: "Use Repowise get_overview to summarize this repository" or "What breaks if I change src/auth.py?"

Full setup, every agent, and optional model-written prose →

---

Your agent stops guessing

Every question your agent asks about a repository has an answer that could have been computed ahead of time. Who calls this function? What breaks if I change it? Why is it written this way? Which files are actually dangerous? Without an index, the agent rediscovers that answer on every task: grep, read, re-read, forget.

Repowise exposes ten task-shaped MCP tools to Claude Code, Codex, Cursor, VS Code and anything else that speaks MCP: graph, git, docs, decisions, and ten MCP tools behind one index. See the canonical surface. Most tools are built around data entities (one file, one symbol), which forces agents into long chains of sequential calls. These are built around tasks: pass several targets in one call, get complete context back.

Because the exploration work is already done, that phase mostly disappears. In a measured agent loop across 43 questions on django/django, Repowise cut the agent's own output by 31.6% (p<0.0001) and reached the answer in 3.8 tool calls instead of 7.2. That is the end-to-end result.

One mechanism is much larger but narrower: loading a commit's context through get_context costs 393 tokens instead of 13,984, or 97.2% less. That is one retrieval payload, not a claim of 97.2% total agent savings. Both measurements and every competitor row are published in the benchmark report.

And it arrives without being asked. Optional hooks push context into the session at the moment it matters: the governing architectural decision when your agent edits a file that decision covers, a warning when it touches a file with a run of recent bug fixes, a compact briefing at session start. Repowise also generates your CLAUDE.md and AGENTS.md from the real index, so even an agent with no MCP support starts informed.

It learns from how you actually work. Switch on transcript capture (repowise decision source set session --on) and Repowise reads your own agent transcripts for the corrections you keep making ("use the shared HTTP client, not raw requests"), turning the durable ones into tracked decisions it delivers back later. Transcripts never leave your machine; one batched model call per update turns the candidates that clear the deterministic gates into records, and --no-llm keeps the gates and drops that call. The wiki generation budget tilts toward the modules you and your agent ask about most, with no switch needed.

<details> <summary><strong>What the index builds</strong></summary>

| Foundation | What it contributes | |---|---| | Graph | File + symbol dependencies across 26 AST-parsed languages, confidence-stamped call resolution, communities, centrality, cycles, and execution flows | | Git | Hotspots, ownership, co-change, bus factor, and bug-fix history: behavioral signals static analysis cannot see | | Docs | A wiki for every module and file, rebuilt incrementally with freshness and confidence scoring plus hybrid search | | Documentation drift | Your own markdown checked against the tree: the claims each document makes, resolved against the graph, and the ones the code refutes | | Decisions | Architectural rationale mined from five index-time sources plus human and agent capture, each claim traced to evidence | | Code health | 51 deterministic detectors across defect risk, maintainability, and performance, followed by concrete refactoring plans |

The structural wiki needs no model. Model-written prose is an optional upgrade, one page or directory at a time. Six of the seven decision sources are deterministic too; only comment archaeology needs a provider.

The intelligence layers → · How the graph earns trust →

</details>

Also: stop paying for output nobody reads

Most of what an agent reads back from a shell command is noise: 300 lines of passing tests wrapped around 4 failures, full commit bodies when it asked "what changed recently". repowise distill <cmd> compresses command output before the agent reads it, errors first, exit code preserved.

repowise distill pytest          # 61% fewer tokens, all 11 failure lines kept
repowise distill git log -50     # 89% fewer tokens
repowise saved                   # what distillation saved you, in tokens and dollars

Nothing is lost. Every omission leaves an inline [repowise#<ref>] marker that repowise expand <ref> reverses in full, so the agent can always pull the detail back without re-running the command. Small outputs pass through untouched. An opt-in hook rewrites noisy commands automatically, shown to you for approval first.

<div align="center"> <img src=".github/assets/savings.png" alt="repowise Costs dashboard: tokens and dollars saved across distill and the MCP tools" width="100%" /> <p align="center"><sub>The <strong>Costs</strong> dashboard tallies both savings surfaces. Every event is priced from the model that produced it, never repriced at whatever you are running today, and the