The run map

The run map draws one run as a tree: every step and sub-agent in order, each annotated with the model it used, its tokens, its cost, its time, its searches and the strength of its evidence, and where it waited for a sign-off.

Reading the run map

Open a run from Agents → Activity or Insights → Runs.

• The tree: the run at the root, then each agent, then each step: model calls, tool calls, searches, approvals, grounding and screening checks, and deliveries.
• Per node: status (ok, error, running), duration, model, input and output tokens, cost, and counts in and out.
• Searches: how many, the passages returned, the tokens sent and the tokens not sent.
• Evidence: claims, the share at the ladder’s strong tiers, and the share uncited. See Evidence.
• Sign-offs: a step waiting for a person stays in Active now; it is not stalled.

A model call is placed under the step that was open when it ended. A call that fits no step stays on the run’s own node and is counted, never guessed into a sibling.

The map is counts, timings and identifiers only. It holds no prompt, answer or document text.

The router’s explanation per step

Showing why the router chose each step’s model on the map is Coming. See The model router.

In the API

GET /api/v1/runs/{run_id_hash}/map returns the same tree. For runs in progress, GET /api/v1/runs/active sends an ETag that leaves out the clock, so a page polling every few seconds gets 304 Not Modified until something happened, and GET /api/v1/runs/active/stream streams them. See Run Map, and the MCP tool run_map.

Sharing a run

Share the run’s address in LightHouse: anyone in your tenant with access can open it. A link outside your tenant does not open. A shareable export of one run is Coming.