Enhance documentation
enhance-dev fixture screen
Upload one captured page and return its reusable screen id.
enhance-dev fixture screen
enhance-dev fixture screen [options]Arguments
This command takes no positional arguments.
Options
| Option | Required | Default | Meaning |
|---|---|---|---|
--file <path> | Yes | None | File containing the captured HTML bytes. |
--client-token <uuid> | No | None | Stable UUID to reuse when retrying the exact same mutation. |
--route <url> | No | None | Original page route retained with the captured screen. |
--page-title <title> | No | None | Page title retained with the capture or used for a new canvas. |
--width <pixels> | No | 1440 | Captured viewport width. |
--height <pixels> | No | 900 | Captured viewport height. |
Input
This command takes its input from the options above. It has no published input schema.
Output
This command writes JSON records to standard output. It has no published output schema.
Examples
enhance-dev fixture screen --file <path>Exit behaviour
| Exit code | Meaning |
|---|---|
0 | The command succeeded. |
1 | The command failed for another reason (INTERNAL). A write may have an unknown outcome. |
2 | The command line was malformed. Nothing ran. |
3 | The API refused the input (BAD_REQUEST). |
4 | The credential is missing or expired (UNAUTHORIZED). |
5 | The API refused the request (FORBIDDEN, NOT_FOUND, CONFLICT, RATE_LIMITED). |
6 | A 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.