enhancedocs
For agentsOpen Enhance ↗
CLI commands / enhance-dev screen complete

Enhance documentation

enhance-dev screen complete

Confirm a captured page after its bytes have been uploaded.

↓ Markdown

enhance-dev screen complete

enhance-dev screen complete [options]

Arguments

This command takes no positional arguments.

Options

OptionRequiredDefaultMeaning
--screen-id <string>YesNoneScreen id returned by enhance screen create or fixture screen.
--etag <string>YesNoneETag returned by the signed upload PUT, with surrounding quotes removed.
--json <json>NoNoneComplete procedure input as JSON; do not combine it with field flags.
--client-token <uuid>NoNoneStable UUID to reuse when retrying the exact same mutation.

Input

This command presents the capability screen.complete. It has write effect and single idempotency.

Show complete input JSON Schema
{"$schema":"https://json-schema.org/draft/2020-12/schema","type":"object","properties":{"screenId":{"type":"string","format":"uuid","pattern":"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"},"etag":{"type":"string","minLength":1,"maxLength":200}},"required":["screenId","etag"]}

Output

This command writes JSON records to standard output. Returns a typed screen.complete result from the Enhance API without transport-specific prose.

Show complete output JSON Schema
{"$schema":"https://json-schema.org/draft/2020-12/schema","type":"object","properties":{"screenId":{"type":"string","format":"uuid","pattern":"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"},"storedBytes":{"type":"integer","minimum":1,"maximum":9007199254740991},"uploadedAt":{"type":"string","format":"date-time","pattern":"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"}},"required":["screenId","storedBytes","uploadedAt"],"additionalProperties":false}

Examples

enhance-dev screen complete --screen-id <string> --etag <string>
Show example input
{
 "screenId": "00000000-0000-4000-8000-000000000010",
 "etag": "x"
}
Show example output
{
 "screenId": "00000000-0000-4000-8000-000000000010",
 "storedBytes": 1,
 "uploadedAt": "2026-08-10T00:00:00.000Z"
}

Exit behaviour

Exit codeMeaning
0The command succeeded.
1The command failed for another reason (INTERNAL). A write may have an unknown outcome.
2The command line was malformed. Nothing ran.
3The API refused the input (BAD_REQUEST).
4The credential is missing or expired (UNAUTHORIZED).
5The API refused the request (FORBIDDEN, NOT_FOUND, CONFLICT, RATE_LIMITED).
6A batch finished only in part. Retry with the same --client-token.

Versions

Minimum tested versions: Enhance CLI and MCP runtime 0.1.40, plugin 1.0.38, Node.js 24. No older floor is published.