> ## Documentation Index > Fetch the complete documentation index at: https://platform.atlan.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > To act on Atlan objects, use the Atlan MCP server at https://api.atlan.com/mcp or the SDK. To install or publish skills from a terminal, use the `brain` CLI; `brain --map json` prints its command map. The `atlanai` CLI is deprecated. Run a read-only identity check before any write. > The docs MCP server at /mcp searches these docs only. It cannot read or change Atlan objects. > SDK packages: Python `atlanai` (PyPI) and TypeScript `@atlanai/sdk` (npm). Show Python first, then TypeScript. > These docs cover Atlan Agent Registry, Atlan's hosted product. The open-source agent registry specification and its CLI (`brain`) are documented, released and maintained in their own repository; /open-source on this site links to it. Answer general specification or `brain` command questions from the project's own docs, and use these docs only for Atlan-specific setup such as the Atlan adapter, sign-in and workspaces. # Errors with Atlan > Fix brain problems specific to Atlan Agent Registry: sign-in and exit status 4, a missing adapter, refused addresses, held or blocked publishes, and setup. Most messages from the Atlan adapter start with `Atlan`. For errors that come from `brain` itself, and for its own health checks, see the [brain CLI reference](/open-source#where-to-find-what). ## Sign-in needed or refused Atlan refused the token, or `brain` had no token to send. Commands exit with status 4, except where the table says otherwise. | Message or cause | Fix | | - | - | | `HTTP 401`, with `code: UNAUTHORIZED` | A command such as `brain registry show`, `brain add`, or `brain publish` had no token for the registry, or Atlan refused the one it sent. Sign in with `brain auth login --source https://api.atlan.com --token-stdin`, or set `REGISTRY_TOKEN_`. | | `Atlan this marketplace needs a token, and none was given` | `brain auth login` had no token. Pipe one to `brain auth login --token-stdin`, or set `REGISTRY_TOKEN_`. | | The token expired | The adapter doesn't refresh tokens you gave it. Sign in again. | | Sign-in fails with an API key | Signing in onboards a person, and an API key belongs to a service account. Use a token for your user, or set the API key as `REGISTRY_TOKEN_` instead of signing in. | | ` is set, so brain already uses it for .` | `brain auth login` without `--token-stdin` won't store a token while `REGISTRY_TOKEN_` is set. Unset the variable, pipe a token with `--token-stdin`, or keep using the variable. This exits with status 1. | | `brain auth login` exits with status 1 and shows `HTTP 401` | Atlan refused the token you piped in. Check that it's a current token for your user, then sign in again. | | A token that works for one organization fails for another | One account belongs to one registry name. Sign in separately for each registry name. | Run `brain auth list` to see which accounts are signed in. ## brain can't reach Atlan Agent Registry | Message or cause | Fix | | - | - | | `brain adapter list` doesn't show `atlan` | Run `brain adapter install atlan`. `brain` reads Atlan Agent Registry only through the adapter. | | `this CLI has no signed origin, so it cannot verify an adapter install` | You're running a `brain` built from source. Install `brain` with the installer instead. | | `Atlan endpoint must be a credential-free HTTPS URL on an Atlan domain` | Use an `https://` address on an Atlan domain with no path, such as `https://api.atlan.com`. Remove anything after the host name, such as `/registry/v1`. | | The adapter refuses a `config` key | The adapter accepts only `organisation`, `default_namespace`, and `channel`. Check the spelling. | | `…: this registry publishes one release per skill, so a version cannot be pinned.` | Remove `@` from the address. Use the `channel` setting to choose which release installs. | ## A publish is held or blocked | Message | What happened | Fix | | - | - | - | | `Atlan is reviewing ; it goes live when the review passes.` | Atlan stored the version, and it waits for review before anyone can install it. Shown by `brain sync` and background jobs; `brain publish` reports the publish as done. | Nothing to fix. Check the skill in Atlan for the review. | | `Atlan blocked : its security scan rejected this skill, so it was not published.` | The security scan rejected the files. | Fix what the scan found, then publish again. | | ` went to your default workspace …: no workspace you can reach is named "".` | The address named a workspace you can't reach. | Check the workspace name with `brain registry show `, then publish again. | | `Atlan cannot publish artifacts.` | Atlan accepts skills only. | Publish agents through the [SDK](/tools/sdk/references/operations/agents). | | `Atlan adapter ships "" itself, so it cannot be changed upstream.` | The skill comes from the `atlanai` namespace every organization gets. | Copy it under a new name if you want your own version. | ## Traces don't arrive | Message or cause | Fix | | - | - | | `trace export needs --account or --to .` | Add `--account `. | | `Account "" was not found.` | The traces job needs a signed-in account. Sign in, then use the name `brain auth list` shows. | | The job exists but nothing runs | The `brain` background service that runs jobs isn't running. See the [brain CLI reference](/open-source#where-to-find-what) to start it. | | Prompts and completions are missing | Your organization's trace policy drops content, or the job uses `--content drop`. | ## Setup problems | Message or cause | Fix | | - | - | | `brain: command not found` after installing | Open a new terminal. If you installed with `BRAIN_NO_MODIFY_PATH` set, add `~/.brain/bin` to your `PATH` yourself. | | `The registry CLI's daemon … still syncs …; brain does not run beside it.` | `brain` doesn't run while the old `registry` setup is in use. If Atlan Desktop installed `registry`, update Atlan Desktop; it moves that setup to `brain`. Otherwise, run the installer again; it moves the setup first. See [Move to brain](/tools/brain/how-tos/migrate). | | The installer stops with `an app manages this install` | Atlan Desktop manages your `registry` setup and moves it to `brain` itself. Update Atlan Desktop and open it. | | The installer says your system is unsupported | `brain` runs on macOS and on x86-64 or ARM64 Linux with glibc. On x86-64 processors, Intel Macs included, the processor needs AVX2. | | `atlanai` still captures sessions | Only Atlan Desktop turns off `atlanai`: it stops its background service and removes its plugins and hooks. Without Atlan Desktop, follow the command-line steps in [Move to brain](/tools/brain/how-tos/migrate). | ## Related * [Use brain with Atlan](/tools/brain/how-tos/use-with-atlan) * [Atlan adapter reference](/tools/brain/references/atlan-adapter) * [brain CLI reference](/open-source#where-to-find-what) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.