Agent Details
Review an agent's governance fields, the systems it connects to, and how it got into the registry
Last updated
Review an agent's governance fields, the systems it connects to, and how it got into the registry
The agent detail view is where you answer the governance questions the registry table only summarises: who owns this agent, which platform it runs on, what it connects to, and how it got into the registry in the first place.
Open it by clicking an agent row in the registry table, or from the Actions menu on that row.
The agent's name sits at the top of the page with three badges beside it:
Status — Active or Inactive
Verification — Verified or Unverified
Risk level — the risk rating recorded against the agent, for example low risk
Click Edit agent at the top right to change the agent's fields. The agent's description sits directly below the header, or No description provided. where nobody has written one.
The Governance section holds the fields a steward needs when reviewing an agent:
Owner
The person accountable for the agent, or Unassigned
Source
The agent source the agent belongs to
Platform
The platform the agent runs on, for example Snowflake Cortex
Model
The model the agent runs on
Environment
Where the agent runs, for example Production
Lifecycle stage
Where the agent sits in its lifecycle
Agent type
The kind of agent, for example Assistant
Registration method
How the entry got into the registry — either registered manually, or discovered by a scan, with the source scanned and when it was first seen
Fields nobody has filled in show a dash (—). A discovered agent arrives with whatever the platform exposes and leaves the rest empty until a steward sets it, so expect gaps on a freshly scanned agent.
Connected Systems lists what the agent reaches.
Each entry shows the connected asset alongside its type and how the link was established, for example source · declared.
Where nothing has been resolved for an agent, the section shows an empty state. Read that as "we don't know what this agent reaches", not "this agent reaches nothing".
The Activity section shows three values:
First seen
When the agent first appeared in the registry
Last activity
The agent's most recent activity signal.
Open incidents
The number of open Decube incidents associated with the agent
A scan fills in only what the platform exposes about an agent. Everything else stays empty until a steward sets it — use Edit agent to complete the record.
The platform hasn't given Decube a last-run signal for that agent. It does not mean the agent is idle.
Source is the Decube source the agent belongs to, and matches the chip next to the agent's name in the registry table. Platform is the agent technology it runs on, such as Snowflake Cortex.
Last updated