Skip to main content
Inspecting a session reads one agent run back from the Registry: the agent’s session list, a session’s metadata, and its full transcript. Use it to check what a run did or to confirm a recorded session is stored as expected. To read the run’s spans and timing instead, see How trace inspection works.

Before you begin

Before you start, make sure you have:
  • Bearer credential and shell variables: ATLAN_GATEWAY_URL and ATLAN_TOKEN set in your shell. See Connect to Atlan Trident.
  • Agent ID: The AGENT_ID of a registered agent whose sessions you want to inspect.
  • Session ID (optional): If you already know which session to read, export SESSION_ID now. If not, the first step below retrieves it.

Inspect your sessions

1

List sessions for your agent

Filter sessions by agent to see all runs the Registry has recorded for it. Pass subject_kind and subject_id as query parameters.
The response is a paginated list. Each item includes the session id, name, session_status, model_id, stop_reason, and source_created_at. Pick the session ID you want to inspect and set it:
2

Read session metadata

A session record holds everything about the run except its messages: which agent ran, which model was used, how it ended, and when it happened.
Key fields to look at:
3

Verify transcript

Messages are stored separately from session metadata. Retrieve them in one call by session ID.
Messages are ordered by sequence_number. Each message has a message_role (user or assistant) and a content field with the turn text.Confirm the message count, roles, and order match what you expect. If messages are missing, check whether they were recorded with the correct session_id path and sequence_number.

Troubleshooting

If the session does not appear under the agent, see Traces appear under person instead of agent. For a duplicated session, see Retried create duplicated session.

Next steps

See also