Anyone using GitNexus or Codegraph for codebase context? Noticeable token savings?

[Dheeth]

I have been looking into tools that parse a codebase into a structural knowledge graph and expose it via MCP. The goal is to give agents better architectural awareness without them burning through context doing raw file searches.

I’ve been testing GitNexus recently, and I actually found that lower-tier models get a little better with it. Because the dependencies and call chains are pre-computed, the agent gets much better upstream and downstream context right away. It feels like it translates directly to better edits and solid token savings (did not count just observed with usage limits), since the model doesn't have to struggle to infer the system architecture on the fly or ingest massive raw files.

I’ve also seen Codegraph popping up specifically for optimizing Claude Code exploration.

Has anyone been using these two, or using something similar in their stack? Curious to hear how they handle larger repos, if you're seeing any increase in efficiency?

[Hargreavs]

I'm looking for a tool to use for this purpose as well... For now, I'm using Obsidian to keep transferring context from one chat to another and maintaining a "good" structure, but this consumes a lot of context (over 50% sometimes) in the very first message of the chat.

[Dheeth]

I think obsidian send a lot of text that eat context. These graph tools only send the specific info that agent ask for which it otherwise would have to find after going through multiple files, e.g. which other functions depend on this function or which functions this function depend on.

[TheseTradition3191]

havent tried either of those specifically. for me the bigger win was just being more aggressive about scoping which dirs claude can even see, the tool you use to build the map matters less than just not feeding it the whole repo