> ## 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.
# Claude Code trace plugin
> Capture local Claude Code sessions as OpenTelemetry traces in Agent Registry.
The `atlanai` plugin installs hooks into Claude Code that record each coding
session and export it to Agent Registry as OpenTelemetry traces. Sessions,
tool calls, subagent runs, and cost appear next to your other agent activity,
with no change to the code you are working on.
**Preview.** The `atlanai/claude-plugins` marketplace is private during
preview, so only authorized testers with repository access can install it
today. macOS and Windows artifacts are not yet natively signed, so this
channel is **not approved for production rollout**. Confirm the current
channel with your Atlan contact.
This is not the MCP integration. Installing this plugin captures your sessions;
it does not add Atlan tools to Claude Code. For tools, see
[the Claude Code integration](/integrations/claude-code). You can use both.
## Before you start
* A current Claude Code installation.
* Access to the `atlanai/claude-plugins` repository during preview.
* An Atlan account that can sign in through the browser.
* On a managed device, follow your organization's software-installation policy —
your administrator may deploy this centrally instead. See
[Managed installation](/plugins/managed-installation).
Check whether the CLI runtime is already present, since Atlan Desktop can
prepare it:
```bash theme={null}
atlanai version
atlanai doctor
```
## 1. Install the plugin
In Claude Code:
```text theme={null}
/plugin marketplace add atlanai/claude-plugins
/plugin install atlanai@atlanai
```
The plugin ships a wrapper that selects a packaged bootstrap for your platform
— macOS, Linux, or Windows on `amd64` or `arm64`. Before activating anything,
the bootstrap verifies:
* an Ed25519 signature over the channel manifest
* the size and SHA-256 digest of the selected runtime and launcher
* the declared native signature policy for the channel
* a runtime self-check
Only then does it activate the runtime, atomically. A failed check leaves the
previous runtime in place.
## 2. Sign in
Authentication is a separate, explicit action — installing the plugin does not
sign you in.
```text theme={null}
/login
```
This runs a browser-based OAuth PKCE flow. Until you complete it, hooks journal
sessions locally rather than discarding them, so work done while signed out is
not lost.
## 3. Verify the installation
```text theme={null}
/status
```
`/status` reports the daemon state, authentication state, and integration
diagnostics. A stopped daemon does not prevent the other checks from running.
```text theme={null}
/doctor
```
`/doctor` runs the launcher's own diagnostics. Neither command prints
credentials, tokens, or local paths.
## Expected result
After signing in and completing one Claude Code session, that session appears in
Agent Registry with its tool calls and subagent activity. Confirm it end to end:
1. Run `/status` and confirm both the daemon and authentication are healthy.
2. Complete a short coding session in Claude Code.
3. Open Agent Registry and find the session under your coding-harness activity.
A healthy `/status` proves local capture is wired up. It does not prove
ingestion — check that the session is actually visible in the expected
workspace before relying on it.
## What gets captured
The plugin registers hooks on these Claude Code events:
`SessionStart`, `SessionEnd`, `UserPromptSubmit`, `PostToolUse`,
`PostToolUseFailure`, `PreCompact`, `PostCompact`, `SubagentStart`,
`SubagentStop`, `Stop`, and `StopFailure`.
Content capture currently defaults to **on** — prompts and tool payloads are
recorded, not just event metadata. Project and environment capture controls
are applied before durable ingestion. Review your organization's policy
before installing this on work that includes sensitive material.
## Where state lives
Durable runtime, OAuth credentials, the SQLite journal, the cursor, and the
outbox live in Atlan's platform-specific application directories — never in
Claude's plugin cache. That has a consequence worth knowing before you
uninstall:
Removing the marketplace stops new hook delivery but **retains historical
state**. Purging that state is a separate, explicit action.
## Commands
| Command | What it does |
| --------- | ------------------------------------------------------------ |
| `/login` | Sign in through the browser. |
| `/logout` | Sign out. Does not delete trace state. |
| `/status` | Daemon state, authentication state, integration diagnostics. |
| `/doctor` | Launcher diagnostics, including `integration doctor`. |
## Limitations
* Preview channel only: macOS and Windows artifacts are not natively signed
yet, so this is not approved for production rollout.
* The marketplace is private until the rollout gates complete. The same
commands work anonymously once the repository is public.
* Claude's organization chat and Cowork marketplace is a separate surface.
Installing there is not the same as local Claude Code tracing and should not
be assumed to provision Claude Code hooks.
* `channels/stable` requires native Apple and Windows signatures plus the Linux
Sigstore policy. `channels/preview` may use manifest-only macOS and Windows
artifacts and is never an implicit fallback from stable.
## Related
Deploy across a fleet with managed settings.
Add Atlan tools to Claude Code — a separate surface.
What a captured session looks like.
Sessions arriving in the wrong place.