Skip to main content
← VS Code Extension

Execution Path

Travsr Execution Path panel

The Execution Path panel traces how one symbol reaches another in the graph: the Dijkstra lowest-cost path between them, plus a λ-corridor of nearby context nodes. Open it with Travsr: Show Execution Path from the command palette or the ⋯ overflow menu of the Travsr Graph view.

Usage​

  1. Place your cursor on a symbol to pre-seed it as the source.
  2. Run Travsr: Show Execution Path from the command palette.
  3. Confirm or edit the source symbol, then enter a sink symbol (the destination).
  4. Travsr computes the lowest-cost path and renders it in the graph panel. If there is no route, a notification gives the reason in Travsr's own words: the two symbols resolved but no call chain connects them, a symbol did not resolve, or the call-edge index is still being built.

What the path shows​

The panel draws the route only: every intermediate node on the lowest-cost route from source to sink (call edges, import edges, and type references), in order. The corridor of nearby context nodes is not drawn, because those nodes are near the route but not on it; the get_execution_path MCP tool returns them under a separate heading.

Backed by get_execution_path​

The panel calls the get_execution_path MCP tool. Results are rendered in the visual graph panel (Cytoscape.js).

Command​

Travsr: Show Execution Path

Available from the ⋯ overflow menu of the Travsr Graph view.