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

# Work with Registry from the CLI

> Find workspaces and inspect agents, harnesses, and other artifacts from the terminal.

Start with read-only discovery before creating or archiving Registry content.

## Find workspaces and artifacts

```bash theme={null}
atlanai workspace list --query "platform"
atlanai search "customer support" --limit 20
atlanai agent list --limit 20
atlanai harness list --limit 20
```

`search` spans searchable artifact kinds but does not include skills. Use
`atlanai skill list` for skills.

List commands share filters, projections, sorting, workspace scope, and
structured output where the backing resource supports them:

```bash theme={null}
atlanai harness list \
  --workspace workspace_123 \
  --filter 'status=active' \
  --fields id,name,description \
  --sort -updated_at \
  --limit 50
```

Use `--all-workspaces` to make account-wide intent explicit. Server totals can
be larger than visible rows because access filtering is applied after the
count.

## Inspect one harness

```bash theme={null}
atlanai harness get harness_123
atlanai harness versions harness_123
```

Autonomous agents and human-driven harnesses are separate artifact types. Use
[`atlanai agent`](/tools/cli/references/commands/agent) to validate, create, search, inspect, or
update an agent definition.

## Archive a harness

```bash theme={null}
atlanai harness delete harness_123
```

The command asks for confirmation. Archiving removes the harness from default
discovery without erasing its history. Use `--confirm` only after resolving the
exact target.