doctl harness-runtime approve
Generated on 1 Oct 2026
from doctl version
v1.177.0
Usage
doctl harness-runtime approve <session> <request-id> <approve|reject|defer> [flags]Description
Resolve a pending approval without attaching: approve, reject, or defer. For an MCP elicitation that asks for values (a data form), pass --content with a JSON object matching what it requested — a plain approve with no --content is only correct for a yes/no approval or an OAuth link, not a form.
Example
doctl harness-runtime approve sess_abc123 req_1 approve;Flags
| Option | Description |
|---|---|
--content |
A JSON object answering an MCP form elicitation’s requestedSchema (e.g. ‘{“site_url”:“https://acme.atlassian.net”}’). Required when the pending request is a data form, not a plain approval. |
--help, -h |
Help for this command |
Related Commands
| Command | Description |
|---|---|
| doctl harness-runtime | Managed Agents Runtime Services (M.A.R.S) |
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 |