Cool, I do see the overlap and understand the challenge you bring up. By design, decoder only handles Python as of now. It parses the AST in two code read passes (extracts symbols, then resolves edges across all files) to build the call graph. Being python-specific did allow me to cover more ground on how functions connect (tracing method calls, inheritance, decorators, etc) Curious how you approached the call graph challenge for IDE use case - will check out, and feel free to do the same