Skip to content
Agents tracked: 502 Releases (7d): 762 Agent status: no reported issuesSince last limit reset: Claude 11d · Codex 9d For AI agents: Markdown Updated Nov 22, 2026

Repowise

by repowise-dev

a map of your code for AI assistants.

Git, GitHub and code reviewOfficialRemote

GitHubWebsite

1. Made by

“"name": "dev.repowise/repowise",”

The server is published by the Repowise team from its own GitHub organization (repowise-dev), the registry name is on its own domain repowise.dev, and the README links the hosted service at repowise.dev.

github.com/repowise-dev/repowise/blob/db12feee74bbff347ea66344c23c113517ed21f6/server.json

Checked against its repository at one commit, on Nov 10, 2026. Tap a verdict to see its source.How we checkedReport an error

What Repowise does

Repowise reads your whole codebase and its change history once, on your own computer, and keeps what it learned in a local index. Your AI coding assistant then asks that index what calls what, what may break and which tests to run, instead of opening file after file. The basic setup is free, needs no key and makes no calls to an AI model.

What people use it for

A tour of an unfamiliar codebase

You inherit a project or open someone else's code. Ask your assistant for a tour and it gets the main parts, entry points and riskiest files in one answer.

Check what a change may break

Before you edit an important file, your assistant asks which other files depend on it, which files usually change with it and which tests to run.

Review a branch before merging

Ask what your branch made worse and which tests cover the changed lines. The answer comes from the code and its history, with no AI model, so the same change gets the same answer.

Decide what to clean up first

Get a ranked list of the weakest files, with concrete cleanup plans, and a list of code that nothing uses any more.

Find out why code is built this way

Before rewriting something odd, ask why it is like that. Repowise looks for recorded decisions and falls back to the change history.

Shorter sessions on a big project Idea

On a large codebase where the assistant keeps rereading the same files, let it ask the index first. This can save time and usage on long tasks.

Repowise popularity

8,170
GitHub stars, repowise-dev/repowise
6,329
downloads last week, repowise
0
public agent projects connect it
Repowise: downloads per weekPyPI, repowise 6,329
Repowise: GitHub starsrepowise-dev/repowise 8,170

Tools it gives your agent (18)

What it sends and its license

Sends

anonymous usage events (command and tool names, versions, OS, a random install id; no code or paths)

To Repowise; after each command and tool call, from a detached sender; kept 90 days. Opt out: repowise telemetry disable, DO_NOT_TRACK=1, REPOWISE_TELEMETRY_DISABLED=1 or REPOWISE_OFFLINE=1.

Sends

code-derived prompts for written docs, decision extraction and refactoring code

To the model provider you configure with your own key (Repowise does not proxy); only when prose or refactoring generation is turned on. Opt out: index with --no-prose and leave generate_refactoring_code off; or use Ollama with a local embedding model.

Sends

a release check against PyPI and the dashboard download (about 50 MB) on the first repowise serve

To PyPI and the Repowise download source; on CLI runs (release check) and the first dashboard start. Opt out: REPOWISE_OFFLINE=1 skips the release check; --no-ui starts the server without the dashboard.

Free under the AGPL-3.0 license for people, teams and companies that use it inside their own work. Building it into a product you sell to others without the AGPL duties needs a paid license from Repowise.

In a paid app
Yes

Using Repowise inside a company, including on code for a paid product, is free under the AGPL.

“Using Repowise inside your company under the AGPL creates no obligation to publish your own code.” source

inside-app-bundle
With conditions

Shipping Repowise inside your own product means AGPL duties, or a commercial license from Repowise.

“workflow integrations, priority support and SLA, or embedding Repowise in a product without AGPL obligations), see” source

Pass on its files
With conditions

Passing on copies or changed versions follows the AGPL-3.0 terms; a commercial license is the other route.

“AGPL-3.0. Free for individuals, teams and companies using Repowise internally.” source

client-work
Yes

Running it on a client's code on your own machine is internal use under the AGPL.

“AGPL-3.0. Free for individuals, teams and companies using Repowise internally.” source

Is it alive

Latest version

0.61.0 in the registry, updated Nov 13, 2026

Last release

0.60.1 (PyPI, 2026-11-02)

Remote endpoint
no remote; the server runs on your own computer

Alternatives

Repowise This page

8,170 starsRemote

repowise

Pick it if you want the same analysis hosted, for private projects, without installing anything

Local

GitDiagram

Pick it if you only need diagrams and an explanation of a public GitHub project

19K starsRemote

GitHub

Pick it if the assistant should open issues, review pull requests or run workflows on GitHub

34.6K starsRemote

Other servers from the same repository

Repowise (Hosted)

All git, github and code review servers

Get started

Tell your AI assistant

“Install repowise 0.60.1 with uv, run repowise init --yes --no-prose in this project (add --no-editor-setup if I only want to try it), wait for it to exit, then after I restart you call get_overview and summarize the riskiest files.”

Connect it

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.

Mistakes to avoid

Run repowise init on a repo the person only wants to try, which also edits ~/.claude.json, Claude hooks and the git post-commit hook
repowise init --yes --no-prose --no-editor-setup (or REPOWISE_SKIP_EDITOR_SETUP=1) for a trial, CI or sandbox

By default init writes the global Claude entry, hooks and a post-commit hook; the flag keeps writes inside .repowise/.

Call the Repowise tools in the same session right after init
Ask the person to restart the host (or run /mcp in Claude Code), then call get_overview

Hosts read MCP config only at startup.

Run repowise generate (or init without --no-prose while a key is set) without asking
Show repowise generate --dry-run first and run generate only after the person approves the cost

Without --no-prose, --yes uses a model when a key is configured, with the cost pre-approved.

Kill repowise init after a fixed tool timeout on a large repo
Run it in the background and wait for the process to exit, then read the exit code (0 ready, 2 gaps, 130 interrupted)

A few thousand files can take several minutes; a cut run leaves the index incomplete.

Call get_execution_flows or set_finding_status on a default server
Opt in first with mcp.tools in .repowise/config.yaml or repowise mcp --tools "+get_execution_flows", then restart

Seven specialist tools are off by default and clients see the surface fixed at server start.

Questions

Does Repowise change my code?

No. The default tools only read the index; one opt-in tool drafts a diff with your own model and another records a verdict in the index.

Do I need a key or an account?

No. The free index needs no key and no account; a model key is only for the optional written docs.

Which assistants work with it?

Claude Code and Codex get every feature; VS Code, Cursor, OpenCode, Hermes, GitHub Copilot CLI and Kiro get the tools plus instructions; any other host can paste a printed config.

How do I turn off the usage counts?

Run repowise telemetry disable, or set DO_NOT_TRACK=1 or REPOWISE_TELEMETRY_DISABLED=1.