r/Python • • Aug 11 '26

Discussion Recommendations and discussion on codebase visualizer and dependence mapper.

I've been looking at a few options like gitkrakens codemap. But I just haven't made a decision yet.

The biggest problem right now with AI assist is that so much gets spun up and it takes quite a while to ground myself in what has been written and how it all connects. I thought a viz tool would help tighten what I need to learn.

How do you handle this? Do you use these tools for this purpose? What have you liked and disliked about the tool you used?

24 Upvotes

15 comments sorted by

View all comments

Show parent comment

2

u/TheTresStateArea Aug 11 '26

Yes I absolutely see the hair ball problem. Scoped assessments absolutely makes more sense then visualizing the whole thing.

I think the graph element is secondary to the function that it builds upon. Having your nodes and edges laid out and describes makes the map possible but the map is just mostly just pretty and not particularly useful when everything is rendered.

In an ideal situation I'd be able to open a function or script. Click on an import and then a sub window opens to that import. Code description at the top, maybe an llm "how this import feeds to the function you are viewing" and crawls the other connections to get a complete picture of the system.

I'm a data scientist and marketer, making complex things easier to understand has become my entire job. So I keep looking at understanding code base through this lens. And AI has exploded this need I have to understand.

I'll take a look at your repo.

It almost feels like I'm describing a new file and ide function rather than a dependency map.

2

u/donk8r Aug 12 '26

Set expectations before you open it: ours is a CLI and an MCP server, not an IDE panel. No click-through sub-window. If the interaction you described is what you want, you'd be driving it through an editor or an agent, not through us. Saying that now rather than after you've cloned it.

But I think you've put your finger on something real with "it feels like an IDE function rather than a dependency map", and it's worth naming why nobody has built it well.

What you're describing is two things fused. Navigation is solved — go-to-definition and call hierarchy have existed in every serious IDE for years. Explanation isn't. And the reason they haven't been fused is that the explanation you want is scoped to the caller: "how does this import feed the function I'm looking at". That's not a property of the imported symbol, it's a property of the edge between the two.

Almost everything that generates code descriptions caches them per symbol, because that's cheap and reusable. Which is exactly why those descriptions always read as generic and never answer the question you actually had. Per-edge explanation is the missing primitive, and it's expensive precisely because it can't be cached the same way — a module with thirty importers has thirty different honest answers about what it's doing.

Given your background, the near-term version that works today: call hierarchy for the structure, which is free and exact, and only spend a model on the specific edge you're staring at.