> ## 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.

# Atlan plugins

> Install Atlan into a coding agent to capture sessions, or install agent artifacts into a project.

Two different tools sit under this heading. They solve opposite problems, and
the names are close enough to confuse, so start here.

|           | Trace plugin                                 | Registry package manager                |
| --------- | -------------------------------------------- | --------------------------------------- |
| Installs  | Atlan into Claude Code                       | skills and plugins into your project    |
| Direction | your sessions flow **out** to Agent Registry | artifacts flow **in** from a repository |
| Command   | `/plugin install atlanai@atlanai`            | `registry add <source>`                 |
| Use it to | see what your coding agent did               | give your agent the skills it needs     |

<Note>
  **Preview.** Both are distributed org-internal today. The
  `atlanai/claude-plugins` marketplace is private during preview, and
  `@atlanai/registry` is not on public npm. Confirm access with your Atlan
  contact first.
</Note>

## Capture coding-agent sessions

The Claude Code trace plugin installs local hooks that turn each coding session
into OpenTelemetry traces and ships them to Agent Registry. You get the same
session, trace, and cost views for coding work that the SDKs give you for your
own agents — without changing any application code.

<CardGroup cols={2}>
  <Card title="Claude Code trace plugin" icon="plug" href="/plugins/claude-code">
    Install the marketplace plugin, sign in, and verify a captured session.
  </Card>

  <Card title="Managed installation" icon="building" href="/plugins/managed-installation">
    Deploy it fleet-wide through Claude Code managed settings.
  </Card>
</CardGroup>

If you want Atlan tools *inside* Claude Code rather than session capture, that
is the MCP endpoint instead — see
[the Claude Code integration](/integrations/claude-code). The two are
independent: connecting MCP does not capture sessions, and installing the
plugin does not add tools.

## Install agent artifacts into a project

`registry` resolves skills, plugins, subagents, commands, hooks, MCP servers,
rules, and LSP servers from a Git repository and projects them into whichever
coding agents a project actually uses — Claude Code, Codex, Cursor, or the
vendor-neutral `AGENTS.md` layout — then records exactly what it did so the next
run can tell whether anything moved.

<CardGroup cols={2}>
  <Card title="Registry package manager" icon="box" href="/plugins/registry-cli">
    Install artifacts, pin refs, and keep a project in sync.
  </Card>

  <Card title="Command reference" icon="terminal" href="/plugins/registry-cli-reference">
    Every command, flag, scope, and exit code.
  </Card>
</CardGroup>

## Related

* [CLI overview](/cli/overview) — the `atlanai` CLI, which owns publishing,
  registry reads, and trace management. It is a different binary from
  `registry`.
* [Publish skills from GitHub](/guides/skills/sync-from-github) — put skills
  *into* Agent Registry, rather than pulling them into a project.
* [Tracing SDKs](/sdk/overview) — instrument your own agents instead of a
  coding agent.