Code Graph

Code Call Graph

LakshX can draw three native maps of your codebase — a call graph (who calls what), a dependency graph (how files depend on each other), and a Guided Tour (an ordered walkthrough of the whole workspace) — all three live in one panel, so you can navigate structure visually instead of chasing references by hand.

Status bar$(graph) Call GraphAnd$(type-hierarchy) Dep GraphAnd$(list-ordered) Guided Tour

Call graph

Place your cursor on a function or method, then open the call graph — from the Call Graph status bar item, or via LakshX: Show Call Graph in the command palette. It builds an interactive call-hierarchy view of what that function calls and what calls it, using the editor’s own language intelligence.

Put your cursor on a symbol first

The call graph starts from wherever your cursor is. If no function is selected, LakshX reminds you: “open a file and place your cursor on a function/method first.”

Dependency graph

Open Dep Graph from the status bar, or run LakshX: Show Dependency Graph, then click Scan workspace— this panel doesn’t scan automatically on open. LakshX walks the workspace and renders a graph of modules, the edges between them, and any dependency cyclesit finds, plus summary stats (files · packages · imports · cycles · orphans) along the top. Click a node to jump straight to that file. A workspace with no scannable source files (e.g. only config/Docker files) correctly shows all-zero stats — that’s the graph reporting nothing to draw, not a broken scan.

Guided Tour

Open Guided Tour from the status bar, or run LakshX: Show Guided Tour. It reuses the exact same scan as the dependency graph (switching to this tab triggers that scan if you haven’t run one yet) and reorders every file/package by role — entry points first, then orchestration, core logic, and shared utilities/persistence last — with a one-line blurb per stop. Use Next/Prev to walk through it top-down, or Jump to file to open the current stop.

When to use it

  • Understanding an unfamiliar codebase before you change it — start with Guided Tour for the top-down walk, then Dependency graph to see how it all connects.
  • Tracing the blast radius of a refactor — everything that calls the function you’re about to touch.
  • Finding circular dependencies you want to untangle.