> ## 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 atlanai CLI; `atlanai --map json` prints its command map. 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.

# Diagnose the CLI

> Inspect installation, daemon logs, privacy controls, and authentication state.

Start with offline checks, then narrow daemon logs to the failing component.

## Check the installation

```bash theme={null}
atlanai version
atlanai doctor
atlanai auth status
atlanai context show
```

`doctor` identifies PATH shadowing, install state, runtime location, Gateway,
credential source, telemetry state, crash-reporting state, and daemon state.

## Read daemon logs

```bash theme={null}
atlanai logs --since 15m
atlanai logs --since 1h --level warn --component api
atlanai logs --follow
```

Use `--grep`, `--until`, and `--tail` to narrow the output. Known credential
patterns are scrubbed, but verbose API logging can still contain request or
response data. Read logs before sharing them.

## Change privacy settings

```bash theme={null}
atlanai config show
atlanai config set telemetry.enabled false
atlanai config set crash_reports.enabled false
```

`ATLANAI_NO_TELEMETRY=1` and `DO_NOT_TRACK=1` override the stored telemetry
setting. Crash reports and usage telemetry are separate controls.

## Collect a support bundle

```bash theme={null}
atlanai trace support bundle ./atlanai-support.json
```

The bundle contains diagnostics, not model content by design. Inspect it before
sending it outside your organization.