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

# atlanai harness

> List, inspect, create, version, and archive harness artifacts.

Harness records describe human-driven runner configurations. Autonomous agent
definitions use the separate `agent` command group.

## Commands

### list

Lists visible harness artifacts in one workspace or across the account.

**Usage**

```text theme={null}
atlanai harness list [flags]
```

| Option | Type | Default | Description |
| - | - | - | - |
| `--workspace`, `-w` | string | account-wide | Scope to one workspace. |
| `--all-workspaces`, `-A` | Boolean | `false` | Make account-wide intent explicit. |
| `--filter` | expression, repeatable | none | Filter fields with `eq`, `ne`, `gt`, `gte`, `lt`, `lte`, `in`, or `contains`. |
| `--fields` | string list | none | Return selected fields. |
| `--sort` | string, repeatable | server default | Sort by field; prefix with `-` for descending. |
| `--limit`, `-L` | integer | server default | Maximum results, up to `500`. |
| `--include-system` | Boolean | `false` | Include system-owned harnesses. |
| `--json`, `--jq`, `--template` | output controls | human table | Select and format structured output. |

### get

Gets the latest or a selected version of one harness artifact.

**Usage**

```text theme={null}
atlanai harness get <id> [--version <ordinal>] [output flags]
```

Shows the latest version unless `--version` is provided.

### versions

Lists every retained version for a harness ID.

**Usage**

```text theme={null}
atlanai harness versions <id> [output flags]
```

### push

Creates a harness or appends a version from a YAML or JSON definition.

**Usage**

```text theme={null}
atlanai harness push <file> [--workspace <id>]
```

The YAML or JSON definition must contain `vendor` and
`default_model_provider`. `--workspace`, `-w` selects the create destination;
otherwise the active context is used.

### delete

Archives a harness while retaining its versions.

**Usage**

```text theme={null}
atlanai harness delete <id> [--confirm]
```

`--confirm` skips the prompt.

Structured reads support `--json`, `--jq`, and `--template`. Valid artifact
fields are `artifact_status`, `created_at`, `description`, `id`, `is_latest`,
`is_system`, `kind`, `metadata`, `name`, `source_digest`, `updated_at`,
`version_ordinal`, and `workspace_id`.

## Examples

```bash theme={null}
atlanai harness list --workspace workspace_123 --json id,name,description
atlanai harness get harness_123 --version 2
atlanai harness push ./harness.yaml --workspace workspace_123
```

## Output and behavior

* List defaults to account-wide when no workspace is supplied.
* Definition-schema errors are reported before a create can succeed.
* `delete` is a soft delete: default listings hide the harness, but versions
  remain readable.
* Empty list results exit with code `0`.

## Related

* [Work with Registry](/tools/cli/how-tos/registry)
* [`atlanai agent`](/tools/cli/references/commands/agent)
* [`atlanai search`](/tools/cli/references/commands/search)
* [`atlanai workspace`](/tools/cli/references/commands/workspace)