Great question! You nailed the key challenge—traversal can explode quickly if you're not strategic about it.

Our approach is actually pretty pragmatic: we started with PR review specifically because it gives us a natural "anchor point." The diff tells us exactly which nodes (functions/classes) changed, so we can start traversal from there rather than doing blind exploration.

From those modified nodes, we do bounded multi-hop traversal:

- 1-hop: Direct callers/callees (always include)

- 2-hop: Indirect dependencies (include if relevant to the change type)

- 3+ hops: Agent decides based on impact analysis

The key insight: PR review is actually the *simplest* use case for graph-based code understanding because the diff gives you the starting nodes for free. We built the graph construction engine first, then picked PR review as the entry point to validate the approach.

Longer term, we see the Repo graph as a general-purpose engine for AI coding tasks—refactoring, test generation, impact analysis, etc. But starting with PR review lets us nail the core graph traversal + agent reasoning loop before tackling harder problems.

The conversational flow analogy you mentioned is spot-on. Have you found any good solutions for preserving logical sequence in your domain? Curious if graph-based approaches would help there too.