# Agents and versions

> Browse your agents, their recorded tools and the activity associated with each version.

**Agents** brings together the tools and recorded runs of each agent in your project. Use it to explore an agent across invocations, or select a version to inspect the behavior of a particular release.

## Open an agent

Select an agent to open its **Agent** and **Metrics** tabs. **Agent** shows the recorded agent description and tools. Choose a version to inspect that release; select a tool to inspect its details and recorded calls, including inputs, outputs and errors.

[![Support specialist agent page with its version selector, recorded tools and recent runs, alongside the application sidebar](/docs/images/platform/agents-overview-dark.png)](/docs/images/platform/agents-overview-dark.png)

Each agent’s page shows the tools and runs associated with the selected version.

Use **Ask Meta Agent** from an agent or tool to investigate with that context. To start from a specific invocation, use **Logs → All agent runs** and [open the run](/docs/platform/logs/runs-and-traces.md).

## Agent identity and versions

Radiant uses the agent ID or name reported by your instrumentation, together with its service identity, to associate runs with an agent. For recognized Claude Code and Codex activity without a reported agent identity, Radiant uses **Claude Code** or **Codex** as the agent name. A service rename can create a separate catalog entry.

Versions come from `gen_ai.agent.version`, or the CLI’s `service.version` for recognized coding-agent activity. They are not inferred from deployment times.

Record a version when you want to distinguish releases in the catalog and compare their [metrics](/docs/platform/logs/agent-metrics.md). The [telemetry reference](/docs/platform/reference/telemetry.md#agent-runs) defines the identity fields and recognition rules.

## Agent recognition

Catalog entries require recognized agent invocation spans and an agent identity, either reported by the instrumentation or supplied by a supported coding-agent mapping. Telemetry that does not meet those requirements remains accessible in **All traces**. Use the [agent-run reference](/docs/platform/reference/telemetry.md#agent-runs) when adapting an exporter or investigating a missing catalog entry.