Skip to main content
The Atlan adapter connects aireg to Atlan Trident. It is installed and updated separately from the CLI. These pages describe the aireg adapter line; the earlier brain adapter uses a different release channel.

Install and update

The CLI verifies the release signature and the downloaded module’s checksum. A source build without a release origin cannot install a signed adapter. Installed adapters update with the CLI’s background update checks unless AIREG_DISABLE_UPDATE_CHECK=1 is set.

Addresses

The adapter accepts atlan.com, atlan.dev, atlan.engineering, and their subdomains. Use https://api.atlan.com unless your administrator provides another origin. The address must use HTTPS and have no embedded credentials, path, query, or fragment.

Registry settings

Unknown keys are rejected. To select a channel, declare it on the registry:
Use a channel that your organization has created. A channel with no release for a skill omits that skill from the installable catalog.

Sign-in and tokens

Sign-in onboards a user. A service account API key is supplied through the per-run variable instead. Background jobs require an account configured for the registry and do not inherit a command’s AIREG_TOKEN_<NAME> variable. A browser sign-in renews itself without Atlan Trident Desktop, and aireg auth logout <registry> ends its session. If you choose a different organization on the sign-in page than the registry’s organisation, the CLI switches the sign-in to the registry’s organization, or fails if your account cannot use it. While the CLI holds a browser sign-in for a registry, the adapter sends it even when Desktop is signed in to the same organization. It is sent only for the organization it was issued for: a registry at the same address declared for another organization is refused until you sign in again. The adapter can refresh an expiring piped user credential through the matching Atlan Trident Desktop session. If that session is missing or no longer valid, sign in again through the browser or Desktop, or supply a new user token. Copying a bearer token to another machine does not copy its refresh session.

Catalog and publication

Atlan commands

These commands are present only with the adapter loaded. See Call Atlan APIs with aireg for input and private output files. Use Capture coding-agent traces with aireg for a complete export and verification flow. See Session outputs for capturing and syncing the files that sessions make.

Trace export options

Session outputs

aireg output captures files that Claude Code and Codex sessions make and syncs them to your personal workspace. A file that fails to upload stays captured on the machine; run aireg output sync again to send it. Paths that look like credentials or other secrets are never captured. aireg output hooks install adds hooks to Claude Code and Codex settings so files are captured as sessions end. A hook that cannot run never fails the session it runs in. aireg output hooks status reports each harness’s hook as installed, outdated, or not installed. Hook capture needs a POSIX shell; on Windows, files sync on the job schedule. When a session publishes a Claude Slides deck, the whole project folder is captured rather than the published file alone: the deck opens at its deck.json index, is named from the title there, and any slide the index lists that is missing from the folder is reported. A slide published from a project that has no deck.json is captured alone, like any other page. A changed file becomes a new version in the personal workspace, and unchanged files are not uploaded again.

Background jobs

All Atlan job types require --account <registry>. The personal-skills job respects a skill you moved out of your personal workspace in Atlan Trident: it stops sending that skill from this machine and reports where it moved instead. Move the skill back to your personal workspace in Atlan Trident to sync it from this machine again. The job rechecks each remembered move after four hours, and resumes at once if the skill is already back in your personal workspace. If Atlan Trident cannot be asked where a skill is, only that skill is held back for a later run; the job still publishes the rest. Check aireg job list before adding a job. For scheduling, the daemon, job history, and generic options, use the aireg CLI reference.

Usage and crash reporting

Installing the Atlan adapter enables its usage events and crash reports. Usage events describe installed artifacts, command and run outcomes, and versions; after sign-in they can include organization and user identifiers. Resolve summaries carry counts only: how often the adapter resolved what to install, the requests it made and how they answered, retries, and how long resolves took. They carry no artifact name, ID, or path. Crash reports use a separate anonymous identifier. Use aireg telemetry status to inspect the settings and aireg telemetry off to disable both. DO_NOT_TRACK and REGISTRY_NO_TELEMETRY also disable them when their value is nonempty and neither 0 nor false. This reporting is separate from trace export and its content policy.