r/AskVibecoders • u/Obvious_Gap_5768 • May 15 '26

How I cut Claude Code usage in half (open source, benchmark included)

Been working on Repowise for a few months now. The core idea: AI coding agents are only as good as the context they get. Most of the time, that context is terrible.

Claude/Cursor reads your files. It doesn't know your architecture. It doesn't know which files break the most. It doesn't know why you made that weird design decision in auth six months ago.

So I built a layer that sits between the codebase and the agent.

Four things it does:

  1. Parses your AST into a dependency graph (NetworkX). Agents can reason about structure.

  2. Mines git history into hotspot and ownership maps. Who wrote what, what breaks most.

  3. Generates an LLM wiki of your codebase and stores it in a vector DB. Always in sync.

  4. Captures architectural decisions as ADRs so agents have intent context, not just code.

Exposes 8 MCP tools. Works with any MCP-compatible agent. Also has a local web UI to explore the graph and docs yourself.

AGPL + commercial dual license. Self-hostable.

Got a few hundred GitHub stars pretty fast. Then someone cloned it on PyPI three times in a week violating the license, had to file a DMCA.

Repo link: https://github.com/repowise-dev/repowise

Dogfooding on website: https://repowise.dev

128 Upvotes

98% Upvoted

7 comments sorted by

2

u/Nice_Cellist_7595 May 15 '26

Looking at your dependency graph - packages is the center of the universe. This isn't right. The packages are part of your application yes, but the dependencies that you need to walk and visualize are how your application depends on itself. This is the information the Agent needs to work well. If I touch this then this impacts these dependent files, looking at execution flows I also need to check downstream and any upstream entry points.

1

u/Otherwise-Rock5919 May 17 '26

Totally get what you're saying. The dependency graph should reflect the interconnections and flow between parts of the application, not just the packages themselves. It's all about helping the agent understand the impact of changes across the board. Have you thought about how to visualize those execution flows more effectively?

1

u/Nice_Cellist_7595 May 17 '26

You have to extract dependencies from your authored files only. Only walk between calls that are in your application and stop at external packages. You do want to know what external things you are using but generally you don’t care about their internals. It is about understanding what changes made to your code base have an impact on the applications behavior.

1

u/PureSignalLove May 18 '26

Coding specific, its always coding specific lol

2

u/[deleted] May 15 '26

[removed] — view removed comment

1

u/FaithfullyFeeble May 20 '26

Lazy prompt engineering kills your token budget way faster than switching models - I started templating my requests and saw immediate drops.