Repowise

decisions once, on your machine. Then you and your coding agent ask it things: what calls this, what breaks if I change it, what is dead, what to fix first, and why it was built this way.

and no tool that finds as much of the graph gets more of it right, in 7 of 7 comparisons. 5 tools · 37,853 compiler edges · every losing row published

Graph, risk, health, tests and dead code make zero LLM calls · no API key needed · free and self-hosted · AGPL-3.0 or commercial

Repowise is an ambitious project. We want every engineer, and every agent working beside them, to understand a codebase the way the person who has maintained it for five years does: what calls what, what tends to break, what nobody uses anymore, and why it was built this way. Cutting tokens was never the goal. It happens anyway, because an agent that can ask the index stops searching, opening and re-reading files to find out. Measured against the other context tools on the same agent tasks, it is also the largest saving.

Set it up in one line

Open Claude Code, Codex, Cursor or any MCP-capable agent in your repository and paste:

Read https://docs.repowise.dev/setup.md and set up Repowise in this repository.

The agent installs Repowise, indexes the repo with no API key, wires itself to the index, and asks you before anything costs money. Prefer to do it yourself:

uv tool install repowise          # or: pipx install repowise / pip install repowise
cd /path/to/your/repo
repowise init --yes --no-prose    # graph, git, health, dead code, docs. No key, no spend.
repowise serve                    # local dashboard + MCP server

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, optional model-written docs →

What it does

One index, three ways to use it. Find the question you came with; each one links to the page that answers it.

Understand the code

Change it safely

Improve it continuously