Here's the problem it solves. On a big repo, Claude greps your files every time you ask it something. It opens them, reads them, works out how they connect, and burns a load of tokens doing it. Then the session ends and it forgets the lot.
Graphify reads your repo once and builds a knowledge graph. Claude queries that map instead of crawling files. Fewer tokens, more accurate answers, and it remembers the structure.
How to try it this week:
1. Install it
Grab the repo (github.com/safishamsi/graphify), paste the link into Claude Code, and say "install Graphify for me." It reads the repo and sets itself up. There are manual steps in the readme but you don't need them. 2. Build the map
Run /graphify . in the folder you're working in. It pulls out your nodes (the pieces), edges (the connections) and communities (clusters of related code). It also shows you the most connected parts of the repo, so you get a tour before you've typed a prompt.
3. Make Claude actually use it
Use graphify query or graphify explain so Claude answers off the map instead of guessing. Run graphify claude install to make it always on.
4. Keep it current
Run graphify hook install and it rebuilds after every commit. That rebuild is free, no API cost, so the map never goes stale.
What you get: Claude stops re-reading your whole project on every question. Cheaper, faster, and it actually knows how things are wired.
Take 20 minutes this week, point it at a repo you actually work in, and ask it the same question with and without the map. Watch the token count.
What codebase would you point it at first?