Give Feedback

doctl harness-runtime config create

Generated on 1 Oct 2026 from doctl version v1.177.0

Copy page as Markdown View page as Markdown

Usage

doctl harness-runtime config create [flags]

Aliases

Description

Create an immutable config from an agents.yaml manifest (same format as doctl harness-runtime create --spec). --name must be unique within your team.

--secret NAME=VALUE (also NAME=@path / NAME=-, repeatable) fills a secret slot the manifest declares. For claude-code, that also satisfies ${ANTHROPIC_API_KEY} in the manifest — the process environment is not required. NAME=- cannot be combined with --spec -. The value is captured server-side against this config and never returned, so sessions started from it need no secrets of their own.

Example

doctl harness-runtime config create --spec agent-spec.yaml --name my-config;

Flags

Option	Description
`--format`	Columns for output in a comma-separated list. Possible values: `ID`, `Name`, `SchemaVersion`, `ContentHash`, `CreatedBy`, `CreatedAt`.
`--help`, `-h`	Help for this command
`--name`	Team-unique name for the config (required)
`--no-header`	Return raw data with no headers Default: `false`
`--secret`	Tenant secret as NAME=VALUE, injected into the manifest’s secret slots (overriding a value declared in the file). Repeatable. NAME=@path reads the value from a file and NAME=- reads it from stdin, so a credential need not appear in shell history or in checked-in YAML.
`--spec`	Path to an agent manifest in YAML or JSON. Prefer flat format (top-level name + agent), e.g. “name: my-config\nagent: opencode”. Set to “-” to read from stdin. ${VAR} references are resolved from the local environment. (required)

Command	Description
doctl harness-runtime config	Manage reusable agent configs

Global Flags

Option	Description
`--access-token`, `-t`	API V2 access token
`--api-url`, `-u`	Override default API endpoint
`--config`, `-c`	Specify a custom config file Default:
`--context`	Specify a custom authentication context name
`--http-retry-max`	Set maximum number of retries for requests that fail with a 429 or 500-level error Default: `5`
`--http-retry-wait-max`	Set the minimum number of seconds to wait before retrying a failed request Default: `30`
`--http-retry-wait-min`	Set the maximum number of seconds to wait before retrying a failed request Default: `1`
`--interactive`	Enable interactive behavior. Defaults to true if the terminal supports it (default false) Default: `false`
`--output`, `-o`	Desired output format [text\|json] Default: `text`
`--trace`	Show a log of network activity while performing a command Default: `false`
`--verbose`, `-v`	Enable verbose output Default: `false`