Skip to main content
A trace is the step-by-step record of one run of an agent or AI tool: its model calls, tool calls, tokens, cost, timing, and errors. A session is one conversation or task, and groups the runs that belong to it. Together they let you answer what an agent did, not only that it ran.

Sessions

A session links its runs to their subject, the agent or harness that ran them. It holds the outcome and timestamps, its events, and its turns: atlanai SDK tracing counts them from the run’s model calls, and an uploaded transcript provides them directly. A session is a record, not a command. Creating one does not start a run, and an uploaded session is final once created: it cannot be edited or deleted.

Traces

Traces are OpenTelemetry data. A trace exists only because something you installed or configured sent it:
  • Atlan Trident Desktop or an aireg traces job: reads the Claude Code and Codex sessions on a computer and sends them, without code changes.
  • atlanai SDK: traces your own agents and their model and tool calls.
  • OTLP exporter: sends traces from any OpenTelemetry setup, including traces imported from another store.
  • A session on the Atlan runtime: the runtime records each run as the agent, with its model calls, tool calls, and outcome.
Ways traces get in compares the routes, where each one’s traces land, and who can see them. Every trace is stored in your organization, and is accepted only for a workspace your credentials can reach.

Attribution

Attribution connects a trace to agents, sessions, skills, and versions. What it can connect depends on the identifiers the source sent. Explicit identifiers are evidence. Missing identifiers mean the link is unknown. For skills, the registry matches the skills recorded in a trace to the skill version with the same content. Each match is an exact match, a SKILL.md match, or a name match, from strongest to weakest.

Where to read them

  • Traces: the turns of your own AI tool sessions, and the runs of every agent you can open.
  • Agent page → Sessions: the recorded sessions for one agent.
  • Agent page → Usage → Recent runs: open a run; it opens on Story, which says what happened and shows each step in plain words.
  • Skill page → Usage: runs attributed to one skill, with their match confidence.

Example

An engineer signs in to Atlan Trident Desktop and fixes a bug with Claude Code. The session reaches Atlan Trident as traces, one for each prompt, in the engineer’s personal workspace. The engineer opens Traces, selects a turn on AI tools, and reads Story: the prompt, each step of the work in plain words, and the response, with each failed step and its reason.

What sessions and traces do not prove

  • A completed run is not a correct answer. A run’s status reports how it executed. Judge the answer with a scorer; see Evaluate agents.
  • An accepted request is not a stored result. A successful exporter or API response confirms one step. Find the matching trace in Atlan Trident and compare its identifiers and timestamps.
  • Missing fields are unavailable, not empty. A trace without a field is not proof that nothing happened.
  • A name is not a version. Do not infer a skill version from its display name.

See also