Skip to main content
aireg is the current AI registry CLI. It replaces the earlier brain name and uses a separately released Atlan adapter. The deprecated atlanai CLI has no new product commands.

Desktop-managed installations

Check the CLI your Atlan Trident Desktop installation manages before changing its files or background service. Desktop versions that manage brain may still use that executable. Upgrade the application through your organization’s normal process. Review the aireg CLI reference for the CLI’s home-directory and configuration details. Do not rename a managed directory or copy credentials between CLI homes. A registry alias, its origin, and its stored account must agree.

Set up terminal installation

  1. Install aireg using the project’s installation and access information.
  2. Install the Atlan adapter and sign in.
  3. Run aireg auth list, then aireg registry show <registry> to confirm the expected account and workspace skills.
  4. Install the skills you need using aireg add <registry>/<workspace>.
  5. Run aireg job list before adding trace capture, so you do not create a second job for the same account. Follow Capture traces.
A successful installation does not prove that credentials or background jobs migrated. Verify each account and trace destination independently.

Command changes

For an old atlanai setup, check that its plugins, coding-agent hooks, and background service have been retired through your Desktop upgrade or your organization’s deployment process. Otherwise two collectors can export the same sessions. Keep the existing setup until the replacement account and trace capture have been verified.

Verify move

Check aireg --version and aireg adapter list separately: the CLI and the Atlan adapter have separate releases. Confirm the expected skills in your coding agent. Export one session and check that it appears in the intended Atlan workspace. See Atlan CLI errors if sign-in, publishing, or export fails.