Skip to main content
Harness records describe where agents run. agent remains a compatibility alias, but new commands and scripts should use harness.

Commands

list

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

get

Gets the latest or a selected version of one harness artifact. Usage
Shows the latest version unless --version is provided.

versions

Lists every retained version for a harness ID. Usage

push

Creates a harness or appends a version from a YAML or JSON definition. Usage
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
--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

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.