Introduction

The registry table is the inventory view: one row per registered agent, with enough signal beside each to tell you whether it is behaving. Most of the columns are properties of the record. Five of them are not, and knowing which five explains most of what looks odd about this screen.

Where to find it

AI Governance > Agent Registry.

The columns

Column	Shows	Where the value comes from
`Agent name`	The registered name	The record
`Platform`	The connected application's logo and name	The record's application, resolved by lookup
`Status`	`Active` or `Setup Pending`	Derived, not stored
`Last trace`	When telemetry last arrived	Telemetry
`Activity`	Trace volume in the window	Telemetry
`Cost`	Spend attributed to this agent	Telemetry
`Incidents`	Incidents raised on it	Telemetry
`Policies`	Policies currently covering it	Telemetry
`Workspace`	The project the record lives in	The record, resolved by lookup
`Owner`	The accountable person	The record, resolved by lookup
`Last updated`	When the record last changed	The record

Two kinds of column, and why it matters

The five middle columns — Last trace, Activity, Cost, Incidents, Policies — are not fields on the agent record. They are computed from telemetry and resolved separately from the row itself.

Two things follow, and both are normal:

They can arrive after the row does — The list renders as soon as the records load. The telemetry columns fill in behind them.
They answer a windowed question, not a lifetime one — "Activity" is volume over a period. A long-lived agent that has been quiet lately reads as quiet, which is the intended behaviour — but it is not the same as "this agent has never run".

Note: A blank telemetry cell is a statement about telemetry, not about the agent. An agent with a Setup Pending status has no traces yet, so every one of these five is empty by definition. That is the expected reading, not a fault.

The Workspace column may not be there

Workspace hides itself unless two things are true at once: you are looking at the all-workspaces view, and you hold read access to projects globally. In a single-workspace view every row would carry the same value, so the column is dropped rather than repeated.

If a colleague sees a column you do not, this is usually why — and it is a permissions difference, not a preference. See Access & Permissions.

The Owner column can show someone who never claimed it

Owner prefers the person picked at registration. For records created before an explicit owner field existed, it falls back to whoever created the record.

So a name in this column means one of two quite different things: someone accepted accountability, or someone once clicked Register. If ownership matters to you — and for anything compliance-facing it does — treat inherited owners as unverified until confirmed. See Ownership, Workspace & Department.

Finding things

Search	Matches the agent name only. Not the description, not the owner.
Default order	Most recently updated first — so a row you have just edited jumps to the top.
Paging	Loads continuously as you scroll, in pages of thirty.
Row click	Opens the agent's detail view.
Row menu	`Delete`, shown only where you hold delete permission on that record.

"Most recently updated first" is a useful default and an unhelpful one for review work: it orders by your team's edits, not by risk. For a governance pass, sort by Incidents or Last trace instead.

What this table deliberately leaves out

The registry lists registered agents. Two things are therefore absent by design:

Excluded assets. An agent you chose not to govern is filtered out. It lives on its connection's detail page — see Review & Triage Discovered Assets.
Models. Discovery returns agents and models together, but they separate here. Models have their own registry, with a different unit of activity.

"The registry is a list of what you decided to govern. It is not a list of what exists."

The Registry Table