get_execution_flows

Runtime call flow, not static structure. get_execution_flows scores the codebase's entry points and traces each one's call graph breadth-first, so the agent sees which functions run in sequence when the program actually executes, and whether that flow crosses architectural community boundaries along the way.

Off by default#

Registered but not part of the default tool surface in any mode. Turn it on per repo:

# .repowise/config.yaml
mcp:
  tools: ["+get_execution_flows"]

or per launch with repowise mcp --tools "+get_execution_flows". See Configuring the tool surface for the full +/- delta syntax.

When to call#

• Orienting in an unfamiliar system: what actually happens when the program runs, beyond the static module map get_overview gives.
• Tracing one entry point: pass entry_point to walk a specific symbol's call chain instead of the top-scored ones.
• Spotting layering violations: crosses_community flags a flow that jumps between architectural clusters.

Parameters#

Returns#

Each flows entry:

Example#

get_execution_flows()
get_execution_flows(entry_point="src/cli/main.py::main", max_depth=4)

Things worth knowing#

• Parameters are bounded. top_n clamps to 1-50, max_depth to 1-20, regardless of what's passed.
• Excluded files never leak downstream. Entry points in excluded paths are dropped up front, and excluded nodes reached later in a trace are filtered out of it too.
• A missing entry_point symbol errors immediately rather than falling back to top-N scoring, so a typo doesn't silently return the wrong flow.