Skip to main content
Use aireg and the Atlan adapter to send Claude Code and Codex transcripts to Atlan. The collector reads the transcripts already on the machine; it does not need hooks in the coding agent. To instrument your own application, use the SDK.

Before you begin

Set up the Atlan adapter and run aireg auth list to find the account name. The examples use atlan. Trace export needs an account configured for that registry; a CI token variable by itself does not create one. Check aireg job list before creating a job. An existing Desktop installation may already run a collector, as a job whose name starts with job_traces_, which stores content unless your organization turned it off. Keep one collector per account and destination. To stop the Desktop collector, run aireg job disable <job>; see Manage trace privacy.
1

Preview local sessions

The preview stays on your machine and does not advance export cursors. It applies the local content setting. It does not demonstrate the final server policy or prove that Atlan has received anything.
2

Choose destination and content policy

Traces go to the account’s personal workspace or its configured default_namespace. Confirm that workspace before exporting.--content drop removes prompts and completions from the export. The default is store. Your organization’s stricter trace policy still applies when sending to Atlan Trident. Usage and crash reporting have separate settings.Artifact uses are recorded whatever the policy. When a session’s calls to Atlan’s MCP tools served a metric or a saved query, the turn that ended in an answer gets one span for each such artifact, marked with how far it took it: returned for a search that listed it, read for a read that brought its definition back, or cited when the turn’s answer names it. A use span carries the artifact’s id, stage, and the tool that served it, with its version and release when the served result named them, and never its name, SQL, or definition. A subagent’s reads count toward the turn that ran it, and a turn that was interrupted or failed records no uses.
3

Export sessions

To export one session, supply its ID, an unambiguous prefix of at least eight characters, or its transcript path:
Add --for claude-code or --for codex to restrict discovery. Unfinished turns and tool calls remain local until they can be finalized. A command that exports no new spans can therefore be correct while a session is active. Codex sessions that Codex archived into archived_sessions/ are read as well, and export continues from where it left off after the move.
4

Verify arrival

Open the destination workspace in Atlan Trident and find the session by its start time. Open its trace and confirm the coding agent and the spans you expected. Matching the workspace and session proves more than a successful local command alone.For a background job, use aireg job runs to inspect its result as well. See Atlan CLI errors if export fails or the session is missing.

Keep exporting in background

After a manual export works, add a job:
The first run can include older local sessions. Add --cwd <folder> to limit which project folders the job reads. Review the aireg CLI reference for scheduling and starting the background service. Check aireg job list and aireg job runs to confirm it is running.