> ## Documentation Index
> Fetch the complete documentation index at: https://platform.atlan.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Read Agent or harness traces

> List, inspect, or aggregate traces for one Agent or coding harness.

# Read Agent or harness traces

Some Gateway deployments expose the Agent extension tool whose source name is
`agent_traces`. It combines trace-list, detail, spans, and statistics reads for
Agents and coding harnesses. Use the exact namespaced name returned by
authenticated `tools/list`.

<Warning>
  This compatibility tool is not declared by the current Agent Gateway `main`
  branch. Call it only when it appears in your connected deployment's
  `tools/list` result. Current deployments can use the public Agent and harness
  trace HTTP endpoints instead.
</Warning>

* Required input: `id`, matching the selected `subject`.
* Subject: optional `subject`, either `agent` or `harness`; defaults to `agent`.
* Operation: optional `op`, one of `list`, `get`, `spans`, or `stats`;
  defaults to `list`.
* Trace scope: `trace_id` is required for `get` and `spans`.
* List options: `start_time_unix_seconds`, `end_time_unix_seconds`, `limit`,
  `cursor`, `sort`, and `user_id`.
* Agent-only list option: `session_status`. Gateway rejects it for a harness.
* Span options: `fields`, `limit`, and `cursor`.
* Statistics: `request` contains the statistics request body. Gateway owns the
  subject scope.
* Common Gateway fields can include `rationale` and `session_id`.
* Effect: read only.

The Agent family resolves traces through recorded sessions. The harness family
uses the harness identity stamped on spans. The creator and organization
administrators can read permitted cross-user results; other members receive
only their own traces.