Call chains

Before you change a script, you want two answers: who calls this, and what does it call? The call chain view gives you both, plus the answer most tools skip: which layout button or trigger actually kicks it off in the first place.

How the view works

Open any script's call chain and you get four lanes, left to right:

1. Entry points: the real-world starts. The layout buttons and script triggers that fire this script, color-coded by kind (button actions, layout triggers, object triggers). This is where "how does this even run?" gets answered.
2. Callers: every script that performs this one.
3. The focal script, highlighted in the center.
4. Callees: every script this one performs.

Click any script chip to jump to its own call chain and keep tracing. When you navigate between linked scripts, the view marks where you came from, so a deep trace doesn't lose you. Pan, zoom, and minimap included.

What it's for

• Impact checks: a script with zero callers and zero entry points is a very different edit than one wired to five layouts.
• Onboarding: trace a solution's main workflow from its buttons down through the scripts that do the work.
• Debugging: something ran, and you need to know all the paths that could have run it.

Related

• The relationship graph: the same exploration idea, for the graph
• Prompt recipes: impact checks in one question