Skip to main content
These pages are for developers and platform teams who want their coding-agent work recorded in AI Registry. A captured session gets the same session, trace, and cost views that the SDKs give your own agents, without changing any application code.

​
Capture methods compared

The trace plugin runs the earlier atlanai CLI, which aireg replaces. Desktop-managed installations can still use brain while the desktop migration to aireg is in progress. To capture sessions with aireg instead, see Capture coding-agent traces with aireg.

​
Core offerings

Capture coding-agent traces

Add an aireg traces job that sends Claude Code and Codex sessions to Atlan.

Claude Code trace plugin

Install the marketplace plugin, sign in, and verify a captured session.

Managed installation

Deploy the trace plugin fleet-wide through Claude Code managed settings.

Trace errors

Fix sessions that land under the wrong identity or workspace.

​
Choose where to start

  • Want Atlan tools inside Claude Code instead? That’s MCP, not session capture: see Connect Claude Code. Connecting MCP doesn’t capture sessions, and capturing sessions doesn’t add tools.
  • Want skills in your coding agents? Use aireg with Atlan installs them.
  • Tracing your own agent rather than a coding agent? Trace your first agent run with the atlanai SDK.
Preview. The atlanai/claude-plugins marketplace is private during preview. Confirm access with your Atlan contact first.

​
See also

  • Move to aireg: Move off the earlier atlanai CLI and its trace hooks.