Relationship Diagnostics

Topology

Topology is a read-only relationship view. It is derived from agent metadata and allowed-subagent configuration, not from observed call volume or latency traces.

/topology

Overview#

The current Topology page helps operators understand which agents are configured to relate to each other. It is useful for sanity-checking structure, spotting isolated agents, and opening a focused side panel for one node.

It is not a trace graph, session replay, or flow analytics page. If an edge exists here, it means the relationship was derived from configuration and metadata. It does not mean the agents actually called each other recently.

Prerequisites#

Prerequisites
  • At least one synced connector or runtime-backed agent so the page has current agent metadata
  • Access to the Web console at `/topology`

Expected Results#

After loading the page, you should see:

  • -A graph view and a table view over the same relationship dataset
  • -Standalone agents separated from connected agents when the page can derive edges
  • -A node side panel with external ID, model, tool profile, allowed subagents, and workspace file hints

Web Operations#

Use the page as a structural diagnostic, not as an observability dashboard.

Graph View

The graph view lays agents out as a configuration-derived relationship graph. Click a node to inspect it. Edges are directional, but they do not encode traffic, latency, or call counts.

Table View

Switch to table view when you need a faster inventory scan. It shows agent name, external ID, health, primary model, allowed subagent count, and tool count without requiring graph navigation.

Side Panel

The side panel is the high-signal operator surface on this page. Use it to inspect the exact metadata driving the relationship view and to confirm whether an agent is intentionally isolated.

FAQ#

Q: Why are there no edges between my agents?
A: The page only renders relationships it can derive from the current metadata. If no allowed-subagent links are present, the agents appear as standalone nodes even if they may still cooperate through other mechanisms.
Q: Does this page prove that one agent called another?
A: No. The page is configuration-derived. It is useful for relationship diagnostics, but it does not prove observed traffic or runtime causality.
Q: Where do I inspect real activity and evidence instead?
A: Use Sessions, Activity, Audit, and Evidence. Those pages are closer to observed operations; Topology is the structural view.
Topology — ClawButler User Manual