Grepai Trace Graph

When you need to understand how deep a function call goes, this builds recursive dependency trees showing what calls what, up to whatever depth you specify. The default two-level depth usually gives you enough context without drowning in noise, but you can crank it up to five if you're debugging something gnarly. It handles circular dependencies gracefully by marking cycles instead of hanging, and the JSON output pairs well with visualization tools if you need to generate architecture diagrams. The compact TOON format is a nice touch for cutting token usage. Honestly most useful during refactoring when you need to see the blast radius of changing a function, or when onboarding to a codebase where the call chains aren't obvious from reading files linearly.